This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ideas:nav-index [2012/08/08 13:06] – fantasai | ideas:nav-index [2014/12/09 15:48] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
There have been a number of concerns raised with the current ' | There have been a number of concerns raised with the current ' | ||
+ | ===== External Issues To Be Incorporated ===== | ||
+ | Extract issues from these and document here as subsections explicitly: | ||
* [[http:// | * [[http:// | ||
* [[http:// | * [[http:// | ||
* Scoping tab navigation indices, so that it can be used in complex pages. | * Scoping tab navigation indices, so that it can be used in complex pages. | ||
+ | |||
+ | More issues: | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | |||
+ | ===== Should HTML specify something ===== | ||
+ | HTML has the tabindex attribute (with various levels of browser support) which has been specified there to some extent: | ||
+ | * http:// | ||
+ | |||
+ | ===== HTML or CSS or both ===== | ||
+ | Does nav-index belong in HTML or CSS or both? | ||
+ | |||
+ | Current thinking: likely both. | ||
+ | |||
+ | HTML already has tabindex (see previous). | ||
+ | |||
+ | CSS should specify nav-index because: | ||
+ | * CSS3-UI already specifies directional nav-* properties | ||
+ | * Any style sheet that explicitly specifies the 2 dimensional directional nav-* properties will likely want to also explicitly specify sequential navigation order as well. | ||
+ | * Keeping both sequential and directional nav-* in the same style sheet will help them stay "in sync" across site changes etc. | ||
+ | * Or rather, having to do them separately in HTML vs CSS will likely cause them to get out of sync. | ||
+ | |||
+ | However, nav-index was in a CSS3-UI CR draft for MANY years and there was no implementation. | ||
+ | |||
+ | Thus only when there is a strong demonstration of implementer interest (2+ commitment to implement) should we consider adding it to CSS4-UI. | ||
+ | |||
+ | ===== within a dialog and browsing context ===== | ||
+ | We should define how to pick the next/ | ||
+ | |||
+ | More details and follow-up: | ||
+ | * https:// | ||
+ | |||
+ | ===== contextual scoping ===== | ||
+ | Need contextual scoping for sequential focus navigation. | ||
+ | |||
+ | More details and follow-up: | ||
+ | * https:// | ||
+ | * http:// | ||
+ | |||