The link should be activated by enter key on focusing the child element inside the anchor(relanding)

Source/core/html/HTMLAnchorElement.cpp

Index: Source/core/html/HTMLAnchorElement.cpp
diff --git a/Source/core/html/HTMLAnchorElement.cpp b/Source/core/html/HTMLAnchorElement.cpp
index 533dc7f200053467398ad4fcd85b52a2a18c06ed..476c99df2663902cc3bf456bbf3c2ee055267acd 100644
--- a/Source/core/html/HTMLAnchorElement.cpp
+++ b/Source/core/html/HTMLAnchorElement.cpp
@@ -147,14 +147,15 @@ static void appendServerMapMousePosition(StringBuilder& url, Event* event)
 
 void HTMLAnchorElement::defaultEventHandler(Event* event)
 {
-    if (isLink()) {
-        if (focused() && isEnterKeyKeydownEvent(event) && isLiveLink()) {
+    if (isLiveLink()) {
+        Node* target = event->target()->toNode();
+        if ((focused() || (target->focused() && contains(target))) && isEnterKeyKeydownEvent(event)) {

[pdr., 2014/10/01 20:32:37]

This does not seem correct.

1) This will break existing content. For example, "<a
href="foo"><textarea></textarea></a>": if the user presses enter in the textarea
to create a new line, they will now incorrectly navigate.

2) Does it make sense for contains(target) to ever be false?

My feeling is that you're in the right area but I am not sure of the correct
solution here.

[robwu, 2014/10/01 21:25:54]

Keyboard input events bubble, so I would expect that the textarea consumes the
Enter and doesn't send it to the parent <a> any more.

This default event handling is implemented in
EventDispatcher::dispatchEventPostProcess. I think that you have to check
whether the Node::willCallDefaultEventHandler(Event) implementations correctly
call Event::setDefaultHandled(true).

             event->setDefaultHandled();
             dispatchSimulatedClick(event);
             return;
         }
 
-        if (isLinkClick(event) && isLiveLink()) {
+        if (isLinkClick(event)) {
             handleClick(event);
             return;
         }