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
If the value of the focusVisible dictionary member of options is true, or is not present but in an implementation-defined way the user agent determines it would be best to do so, then indicate focus.
It doesn't contain the behavior when focusVisible is false.
When element isn't :focus-visible the focus skip indicates focus.
But when element is in :focus-visible state, and call focus( { focusVisible: false } ). Should it switch from :focus-visible to :focus?
I have a case that user uses the keyboard TAB key to focus, then uses the mouse to move and hover interactively.
Expected to hide the focus ring (outline) but don't change the focus element.
I tried to call focus( { focusVisible: false } ), but no effect.
The text was updated successfully, but these errors were encountered:
woody-li
changed the title
Clarify behavior of element.focus( { preventScroll: false } )
Clarify behavior of element.focus( { focusVisible: false } )
Jan 24, 2025
What is the issue with the HTML Standard?
In current specification:
It doesn't contain the behavior when focusVisible is false.
When element isn't
:focus-visible
the focus skip indicates focus.But when element is in
:focus-visible
state, and callfocus( { focusVisible: false } )
. Should it switch from:focus-visible
to:focus
?I have a case that user uses the keyboard TAB key to focus, then uses the mouse to move and hover interactively.
Expected to hide the focus ring (outline) but don't change the focus element.
I tried to call
focus( { focusVisible: false } )
, but no effect.The text was updated successfully, but these errors were encountered: