-
Notifications
You must be signed in to change notification settings - Fork 38
Historical discussions of reordering sequential navigation
Whether and how authors should be provided tools to influence the order of sequential navigation has been brought up in many groups many times. This page is an attempt at documenting them, to save time when someone wants to research the topic. Contributions welcome.
For more context about the need for this, see https://github.com/WICG/spatial-navigation/issues/10
https://logs.csswg.org/irc.w3.org/css/2017-11-07/#e907534
- Sequential and spatial navigation have significantly overlapping use cases. It seems likely that many situations for which reordering of sequential navigation has been described as desired would actually be better solved by having spatial navigation, so working on spatial navigation first seems like a reasonable way forward.
- Spatial navigation involves layout, so it is relevant for the CSS-WG, but it also involves more topics (DOM APIs, Components, A11y…), and therefore should be discussed in a forum distinct from the CSS-WG. WICG seems like a good host, at least initially.
https://github.com/w3c/csswg-drafts/issues/1748
This is a request to add tab-index to CSS, with discussion of the pros and cons and various examples. The discussion includes alternative proposals for nav-pre and nav-next, or nav-order: strutural | visual, as well as a proposal for the ability to scope indices to sub-trees with something like tab-index-group: isolate. Yet another suggestion in that thread is for tab-index: <signed number> | none; tab-index-group: <signed number>;
The discussion also covers an existing polyfill of nav-index by its author.
https://github.com/w3c/csswg-drafts/issues/1764
A split from CSS-WG issue #1748 to discuss one of the specific proposals: nav-order: strutural | visual;
https://github.com/w3c/csswg-drafts/issues/1949
Proposing a nav-context: ignore (default) | relative | absolute; property to scope the index-based proposed sequential-navigation reordering properties to a sub tree.
Initial message by @LJWatson
Key Responses:
- https://lists.w3.org/Archives/Public/www-style/2016Jun/0123.html
- https://lists.w3.org/Archives/Public/www-style/2016Jun/0124.html
- https://lists.w3.org/Archives/Public/www-style/2016Jun/0125.html
Discussion of a possible tab-order: dom | flex property, of how this isn't a flexbox specific problem, of how "visual order" isn't necessarily a single unambiguous thing, and of how spatial navigation may be a better answer.
Initial message by @fantasai
- https://lists.w3.org/Archives/Public/www-style/2012Jun/0478.html
- https://lists.w3.org/Archives/Public/www-style/2012Jul/0046.html
Key Responses:
- https://lists.w3.org/Archives/Public/www-style/2012Jun/0479.html
- https://lists.w3.org/Archives/Public/www-style/2012Jun/0480.html
Discussion about tab-order: tree(or normal) | visual property for making the focus navigation be affected by "visual order".
The discussion ended with the possibility of extending the 'nav-index' property (deprecated for now) in CSS3 UI.
Lorem Ipsum…