This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| ideas:nav-index [2014/02/24 17:00] – note external issues, add a few explicitly with thinking tantek | ideas:nav-index [2014/02/26 16:45] – note HTML spec of tabindex sequential nav, and condition for re-introducing nav-index tantek | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| ===== Should HTML specify something ===== | ===== 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/ | ||
| ===== HTML or CSS or both ===== | ===== HTML or CSS or both ===== | ||
| Line 21: | Line 22: | ||
| Current thinking: likely both. | Current thinking: likely both. | ||
| - | HTML already has tabindex | + | HTML already has tabindex (see previous). |
| CSS should specify nav-index because: | CSS should specify nav-index because: | ||
| Line 29: | Line 30: | ||
| * Or rather, having to do them separately in HTML vs CSS will likely cause them to get out of sync. | * 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:// | ||