27020 2014-10-10 20:15:07 +0000 Sequential focus navigation algorithm should include non-focusable elements 2016-04-20 21:31:56 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX P1 enhancement --- 1 rob dave.null arronei d ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 112971 0 rob 2014-10-10 20:15:07 +0000 The sequential focus navigation algorithm [SFN] only specifies the behavior for focusable elements. This should be extended with non-focusable elements. This is in particularly relevant for reference fragment navigations. E.g. when the user visits page.html#refid (<h3 id=refid>), then the SFN should select the next focusable element *after the refid anchor*, instead of the top of the document. Most implementations (except Firefox) currently jump to the top of the page. This is unnatural, and Chrome wants to implement something like what I described (https://crbug.com/262171). See https://www.w3.org/Bugs/Public/show_bug.cgi?id=26907 and the bottom of https://crbug.com/417636#c3 for more context and test cases. When non-focusable elements are included, other situations need to be accounted for as well, such as: - Element removal (should the SFN continue at the nearest non-disconnected ancestor node, or should the SFN continue at the top of the document?) - Focusing steps (should the node.focus() method affect SFN?) - Change of focusability (e.g. removing the tabindex attribute) [SFN] https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus-navigation 121078 1 mike 2015-06-16 11:35:35 +0000 Raising priority and noting as requiring a minor "feature tweak" to an existing feature. 125976 2 arronei 2016-04-20 21:25:06 +0000 HTML5.1 Bugzilla Bug Triage: This bug constitutes a request for a new feature of HTML. Our current guidelines, rather than track such requests as bugs or issues, is to create a proposal for the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG (https://www.w3.org/community/wicg/). As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process (https://wicg.github.io/admin/intent-to-migrate.html). 125979 3 d 2016-04-20 21:31:56 +0000 This is fixed in the HTML Standard, FYI: https://github.com/whatwg/html/commit/b466ad7ce49676873ddade4c473b7c983803bfd4 (https://github.com/whatwg/html/pull/732)