[Bug 27020] New: Sequential focus navigation algorithm should include non-focusable elements


            Bug ID: 27020
           Summary: Sequential focus navigation algorithm should include
                    non-focusable elements
           Product: HTML WG
           Version: unspecified
          Hardware: Other
                OS: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: rob@robwu.nl
        QA Contact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html-admin@w3.org,

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)


You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 10 October 2014 20:15:09 UTC