Keyboard focus is trapped on .multiselect-options element when search is enabled
See original GitHub issueVersion
- Vue version: 3
Description
When you enable the searchable
option:
- Focus the multiselect field
- Press “tab” to move the focus to the next focusable element
- The
.multiselect-options
element catch the focus instead. This shouldn’t happen since this element is hidden.
Demo
https://codesandbox.io/s/festive-glitter-ujwnh?file=/src/App.vue
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
User focus is not accidentally trapped in a region
Keyboard focus should never be locked or trapped at one particular page element. Users should be able to navigate to and from all...
Read more >What can affect keyboard focus html? - Stack Overflow
Using an element that doesn't normally do something (such as a <span> ) and adding an onclick event to it.
Read more >Using JavaScript to trap focus in an element | hidde.blog
Trapping focus is a behaviour we usually want when there is modality in a page. Components that could have been pages of their...
Read more >How to trap focus inside modal to make it ADA compliant
tab, shift + tab and enter key and focus should be trapped inside modal and should not go out after pressing tab key...
Read more >Keyboard - Accessibility - MDN Web Docs - Mozilla
The tabindex attribute indicates that an element is focusable using the keyboard. A value of zero indicates that the element is part of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed in
1.3.1
. Actually it switched to an option because they are using<a>
which is focusable. Now it should be fine.Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period.