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
The current implementation will only consider non interactive elements if el.tabIndex > 0, but my understanding is that using values other than 0 or -1 is discouraged. I did confirm that using tabindex="1" works, but this makes the focus order inconsistent with the element layout order. Should the check be el.tabIndex >= 0 instead?
Expected behavior
Elements with tabindex="0" set should be focused by JS.focus_first.
The text was updated successfully, but these errors were encountered:
Environment
Actual behavior
I have a custom select input that has a root div tag with
tabindex=0
to allow it to be focused. However, it seems thatJS.focus_first
will not focus this since divs are not considered focusable ifinteractiveOnly
is true.The current implementation will only consider non interactive elements if
el.tabIndex > 0
, but my understanding is that using values other than0
or-1
is discouraged. I did confirm that usingtabindex="1"
works, but this makes the focus order inconsistent with the element layout order. Should the check beel.tabIndex >= 0
instead?Expected behavior
Elements with
tabindex="0"
set should be focused byJS.focus_first
.The text was updated successfully, but these errors were encountered: