When using Spatial Navigation, tab index order should be ignored.
This problem is mostly visible when there is no focused node, e.g. after page load. The algorithm finds the node with the lowest tab index, instead of the first focusable node.
Here is an example:
<a href="#">I am a</a><br>
<div tabindex=3>I have tab index</div>
<div tabindex=2>I have tab index</div>
<div tabindex=1>I have tab index</div>
<div tabindex=4>I have tab index</div>
I tested with Opera, and Opera finds the first <a> element, but WebKit finds the div with tab index 1.
Title changed because fixing the issue is more than ignoring the "index" in tab-index.
A patch is coming soon.
This issue is addressed in the patch in https://bugs.webkit.org/show_bug.cgi?id=49382
*** This bug has been marked as a duplicate of bug 49382 ***
RESOLVED/DUPLICATED ==> no need to block bug 39121 anymore.