You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+++ This bug was initially created as a clone of Bug #23870 +++
FKA (full keyboard access): There is currently no defined way to get keyboard focus into and out of a shadow DOM component. Some components (like the native "number" input type) don't need this, but others (like native video controls) need multiple tab stops inside the shadow DOM component.
For example:
Although there are multiple focusable elements inside (textfield, increment button, and decrement button), all features can be controlled with standard keyboard behavior. Focus stops on the input, and the increment/decrement buttons are activate with up/down arrows.
The text was updated successfully, but these errors were encountered:
Title: FKA: No defined way to get keyboard focus into and out of a shadow DOM component (bugzilla: 24106)
Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24106
comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24106#c0
Silvia Pfeiffer wrote on 2013-12-16 05:27:18 +0000.
+++ This bug was initially created as a clone of Bug #23870 +++
FKA (full keyboard access): There is currently no defined way to get keyboard focus into and out of a shadow DOM component. Some components (like the native "number" input type) don't need this, but others (like native video controls) need multiple tab stops inside the shadow DOM component.
For example:
Although there are multiple focusable elements inside (textfield, increment button, and decrement button), all features can be controlled with standard keyboard behavior. Focus stops on the input, and the increment/decrement buttons are activate with up/down arrows.
The text was updated successfully, but these errors were encountered: