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
When looking through the w3c patterns documentation and playing around with the native HTML select it seems like Tab has some behaviour attached to it that is not present in this library.
The behaviour is that when Tab is pressed, the current "active" value should be selected and then the focus should either move to the next focusable element or the select trigger. I see that the Tab key is disabled on purpose so I was wondering if this would be something that the library should support.
Thanks for the great work!
Additional information
I intend to submit a PR for this feature.
I have already implemented and/or tested this feature.
The text was updated successfully, but these errors were encountered:
Describe the feature
When looking through the w3c patterns documentation and playing around with the native HTML select it seems like
Tab
has some behaviour attached to it that is not present in this library.The behaviour is that when
Tab
is pressed, the current "active" value should be selected and then the focus should either move to the next focusable element or the select trigger. I see that theTab
key is disabled on purpose so I was wondering if this would be something that the library should support.Thanks for the great work!
Additional information
The text was updated successfully, but these errors were encountered: