Shadow host with its .tabindex property -1 would be skipped for focus navigation #556
Assignees
Labels
Comments
TakayoshiKochi
pushed a commit
to TakayoshiKochi/webcomponents
that referenced
this issue
Aug 29, 2016
TakayoshiKochi
pushed a commit
to TakayoshiKochi/webcomponents
that referenced
this issue
Aug 29, 2016
…is -1 The Shadow DOM spec section 6.3 (sequential focus navigation) unintentionally excluded all shadow hosts with nagative tabindex in Step 3.1.3. This was unexpected for shadow hosts with `delagatesFocus=false` shadow root. Before: - Exclude all shadow hosts with tabindex < 0 After: - Allow shadow hosts with tabindex < 0, but only when `delegatesFocus=false` - In sorting by tabindex, treat such shadow hosts as `tabindex=0` - Exclude those shadow hosts in Step 4.
|
@rakina : This issue seems still relevant. |
|
Yes, the whole flat tree will be skipped when the host has negative tabindex value, as currently specced. Is there any interest in changing that? |
|
@rakina : I guess the users of a component decided to set I was thinking about focusing via mouse click and such but those aren't affected by this because we've isolated that to use the first focusable element in the flat tree order. |
|
@smaug---- @annevk : I think we can close this issue now. WDYT? |
|
Yes, if one uses -1 on the host, the shadow DOM shouldn't get focused. Fine to close |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context:
#554 (comment)
In the Shadow DOM spec 6.3
http://w3c.github.io/webcomponents/spec/shadow/#sequential-focus-navigation
specifically in Step 3.1.3, all elements with negative tabindex value will be skipped in the focus navigation, but shadow hosts with
delegatesFocus=faluseshould be excluded otherwise all focusable elements in its shadow root will never visited.The text was updated successfully, but these errors were encountered: