Bug 141136

Created attachment 245826 [details] test case Steps to Reproduce: 1. define a non focusable element: <div id="the-target"> 2. define a link to that element: <a href="#the-target"> 3. click the link, hit <kbd>Tab</kbd> to see where focus ends up Expected Behavior: While the non focusable :target (<div id="the-target">) should not have received focus, it should be the element from which the next item in the document's tabbing sequence is identified upon pressing <kbd>Tab</kbd> What Went Wrong: Focus was retained on the link element, the tabbing sequence continues from there. Related Bugs: https://bugs.webkit.org/show_bug.cgi?id=17450 https://bugs.webkit.org/show_bug.cgi?id=140963 https://bugs.webkit.org/show_bug.cgi?id=17450 Chromium Bug For Reference: https://code.google.com/p/chromium/issues/detail?id=454172 Additional Notes: "navigating to a fragment identifier" [1] defines what should happen when an anchor link is clicked. Using the "sequential focus navigation starting point" [2] is the way Gecko handles :target elements that are not focusable. This behavior renders table of contents and skip-links useless, unless their :target elements are focusable. [1] http://www.w3.org/TR/html5/browsers.html#scroll-to-fragid [2] https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus-navigation-starting-point