There have been a number of concerns raised with the current 'nav-index' property. This page is to document them and the resulting discussions, with the aim of addressing these issues in a future revision of the UI module.
Extract issues from these and document here as subsections explicitly:
More issues:
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
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:
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.
We should define how to pick the next/previous element in sequential focus navigation, to make sure it's clear that it stays within a dialog and browsing context.
More details and follow-up:
Need contextual scoping for sequential focus navigation.
More details and follow-up: