This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28079 - [Shadow]: inappropriate reference to CSS3-UI nav-index spec in focus navigation order
Summary: [Shadow]: inappropriate reference to CSS3-UI nav-index spec in focus navigati...
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Hayato Ito
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 15480
  Show dependency treegraph
 
Reported: 2015-02-23 05:24 UTC by Takayoshi Kochi
Modified: 2015-05-27 02:49 UTC (History)
4 users (show)

See Also:


Attachments

Description Takayoshi Kochi 2015-02-23 05:24:54 UTC
The current shadow DOM spec specifies the focus navigation order of
elements in the shadow tree using CSS3 UI's "nav-index" property[1]
(more specifically in its algorithm 1.3.2 and 2.3, the spec refers to
"auto" for nav-index CSS property).

It's better to rewrite this part to refer to HTML spec, rather than
CSS3 UI spec.


The property is considered "at risk" in the CSS3 UI spec, and might not
be adopted as is in the current spec draft.  I found some discussion in
CSS WG's meeting notes[2].

As far as I read the CSS3 UI spec, the "auto" value corresponds to the
behavior of HTML attribute "tabindex" with its value 0 (cf, the spec
is [3] or [4]), which is already implemented in most browsers and the
spec is stable.

[1] http://www.w3.org/TR/css3-ui/#nav-index
[2] https://lists.w3.org/Archives/Public/www-style/2015Jan/0406.html
[3] https://html.spec.whatwg.org/multipage/interaction.html#the-tabindex-attribute
[4] http://www.w3.org/TR/html5/editing.html#sequential-focus-navigation-and-the-tabindex-attribute
Comment 1 Hayato Ito 2015-05-27 02:49:50 UTC
Moved to https://github.com/w3c/webcomponents/issues/88