W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

[csswg-drafts] Scoping navigation/focus subtrees (nav-dir, etc.)

From: James Craig via GitHub <sysbot+gh@w3.org>
Date: Tue, 07 Nov 2017 19:48:23 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-271960164-1510084102-sysbot+gh@w3.org>
cookiecrook has just created a new issue for https://github.com/w3c/csswg-drafts:

== Scoping navigation/focus subtrees (nav-dir, etc.) ==
Re-adding from https://lists.w3.org/Archives/Public/www-style/2013May/0076.html

As specified, nav-index has the same serious negative implications of positive integer values of tabindex, where in order to be specified usefully, each node has to know about the layout order of every other node in the document. If you're only specifying nav index on first level branches, this is fine, but there is no good way to use this on leaf nodes, and it has severe consequences for breaking index order of keyboard navigation.

This particular problem *might* be solvable with an additional property used on parent or ancestor nodes such as:

	nav-context:  ignore (default) | relative | absolute;

Or potentially by allowing the nav-index context to inherit and cascade. For example:

	[role="toobar"] {
		nav-index: 0; /* retain default tab order until you the user reaches this element or a descendant. */
		nav-context: relative; /* sets the root nav context for this container */
	}
	[role="toobar"] button#b1 {
		nav-index: 1; /* first focusable element within the toolbar; does not override root tab order. */
	}
	[role="toobar"] button#b2 {
		nav-index: 2; /* second focusable element within the toolbar; does not override root tab order. */
	}


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1949 using your GitHub account
Received on Tuesday, 7 November 2017 19:48:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 November 2017 19:48:28 UTC