15529 2012-01-12 03:25:13 +0000 [Shadow]: ShadowHost's tabindex attriblue 2012-01-13 21:19:25 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 14978 1 hayato dglazkov public-webapps-bugzilla oldest_to_newest 62580 0 hayato 2012-01-12 03:25:13 +0000 How should we treat ShadowHost's tabindex attribute? Let me explain by the following example: <input id='A' tabindex='2'/> <shadowhost tabindex='1'> - shadowRoot <input id='B'/> <input id='C'/> </shadowhost> <input id='D' tabindex='3' /> In this case, in which order should we traverse in sequential focus navigation? 1). B -> C -> A -> D (ShadowHost acts like a iframe element, becoming a scope of sequential focus navigation.) 2). A -> D -> B -> C (ShadowHost's tabindex is not honored, every elements are 'flattened'.) 3). Anything else? The spec seems that say 2) is the desired behavior. Note that current WebKit's implementations acts like 1). 62588 1 dglazkov 2012-01-12 04:26:48 +0000 I thought I already spec'd this out: http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#focus-navigation Can you verify and make sure there aren't holes? 62590 2 hayato 2012-01-12 05:58:13 +0000 (In reply to comment #1) > I thought I already spec'd this out: > http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#focus-navigation > > Can you verify and make sure there aren't holes? Thank you. I've read it and understand that the spec clearly mentioned the navigation order. Awesome. Let me ask two questions to make sure that my understanding is correct. My questions come from the different behavior between ShadowHost and iframe. 1). If shadow host is focusable, like: <input id='A' tabindex='2'/> <shadowhost id='B', tabindex='1' (focusable) > - shadowRoot <input id='C'/> <content> <input id='D' tabindex='1'/> <input id='E' tabindex='2' /> </shadowhost> <input id='F' tabindex='3' /> The spec says we should navigate this tree in the following order: Document navigation order: B > A > F Shadow DOM navigation order: D > E > C In total: B > D > E > C > A > F Let me confirm that a shadow host itself (= B) participates in focus navigation, right? 2). If shadow host is not focusable like: <input id='A' tabindex='2'/> <shadowhost id='B', tabindex='-1' (non-focusable) > - shadowRoot <input id='C'/> <content> <input id='D' tabindex='1'/> <input id='E' tabindex='2' /> </shadowhost> <input id='F' tabindex='3' /> Document navigation order: A > F > B (assuming B's tabindex=0 (Does 'auto' means tabindex=0?)) Shadow DOM navigation order: D > E > C In total: A > F > D > E > C Let me confirm that we have no way to skip entire shadow DOM from focus navigation, right? 62603 3 dglazkov 2012-01-12 17:01:28 +0000 (In reply to comment #2) > (In reply to comment #1) > > I thought I already spec'd this out: > > http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#focus-navigation > > > > Can you verify and make sure there aren't holes? > > Thank you. I've read it and understand that the spec clearly mentioned the > navigation order. Awesome. > Let me ask two questions to make sure that my understanding is correct. My > questions come from the different behavior between ShadowHost and iframe. > > 1). If shadow host is focusable, like: > > <input id='A' tabindex='2'/> > <shadowhost id='B', tabindex='1' (focusable) > > - shadowRoot > <input id='C'/> > <content> > <input id='D' tabindex='1'/> > <input id='E' tabindex='2' /> > </shadowhost> > <input id='F' tabindex='3' /> > > The spec says we should navigate this tree in the following order: > > Document navigation order: B > A > F > Shadow DOM navigation order: D > E > C > In total: B > D > E > C > A > F > > Let me confirm that a shadow host itself (= B) participates in focus > navigation, right? > > > 2). If shadow host is not focusable like: > > <input id='A' tabindex='2'/> > <shadowhost id='B', tabindex='-1' (non-focusable) > > - shadowRoot > <input id='C'/> > <content> > <input id='D' tabindex='1'/> > <input id='E' tabindex='2' /> > </shadowhost> > <input id='F' tabindex='3' /> > > > Document navigation order: A > F > B (assuming B's tabindex=0 (Does 'auto' > means tabindex=0?)) It means the absence of index. > Shadow DOM navigation order: D > E > C > In total: A > F > D > E > C > > Let me confirm that we have no way to skip entire shadow DOM from focus > navigation, right? Yup. You've got it. 62688 4 dglazkov 2012-01-13 21:19:25 +0000 Please reopen if this needs more work.