-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keyboard access: add a way to re-open without re-focusing #1054
Comments
@WofWca this had me rethink the structure of the component. #1067 swaps out the root div for a I'm not sure if it will be considered a breaking change or not yet.. The signature of some methods will change, and so will the template, but the consumer implementation is unchanged. |
@WofWca Im not sure if this helps - a bit late commenting but I just came across this as well. |
Adding a listener on arrowDown and arrowUp while input is in focus should open the dropdown in my opinion. This is the behavior I have used in my previous custom made select component. |
I can report that this problem still exists: We use vue-select in one project for displaying a multi-select (a select that allows selecting multiple entries). When the multi-select is focused, it opens (as a drop-down) and all its entries are read by a screenreader. After I selected one entry with the enter key, the focus moves outside of the multi-select to some invisible element and has to be moved back to the multi-select with Shift + Tab. I would have expected that the multi-select is still focused after selecting one entry so that I can directly use the arrow keys and the enter key to select another entry. |
https://vue-select.org/sandbox.html
vue-select
.Enter
).Can't open the dropdown again without pressing
Tab
, thenShift + Tab
.Check out how the native select behaves: https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select
Describe the solution you'd like
Re-open the dropdown when
Enter
is pressed.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: