Differences

This shows you the differences between two versions of the page.

--- ideas:nav-index [2014/02/24 17:15] – add dialog, browsing context, contextual scoping issues tantek
+++ ideas:nav-index [2014/11/19 10:06] – [External Issues To Be Incorporated] dbaron
@@ Line 12: / Line 12: @@
   * http://lists.w3.org/Archives/Public/wai-xtech/2011Nov/0034.html
   * http://lists.w3.org/Archives/Public/wai-xtech/2011Nov/0035.html
+  * http://lists.w3.org/Archives/Public/www-style/2011Nov/thread.html#msg440
 ===== Should HTML specify something =====
-HTML has the tabindex attribute (with various levels of browser support) which should be specified there.
+HTML has the tabindex attribute (with various levels of browser support) which has been specified there to some extent:
+* http://www.whatwg.org/specs/web-apps/current-work/#sequential-focus-navigation
 ===== HTML or CSS or both =====
@@ Line 21: / Line 23: @@
 Current thinking: likely both.
-HTML already has tabindex and thus should specify that (see previous).
+HTML already has tabindex (see previous).
 CSS should specify nav-index because:
@@ Line 28: / Line 30: @@
   * 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 =====
@@ Line 40: / Line 46: @@
 More details and follow-up:
   * https://www.w3.org/Bugs/Public/show_bug.cgi?id=23960
+  * http://lists.w3.org/Archives/Public/www-style/2011Nov/thread.html#msg441