keydown navigation in dropdown broken if there are hidden items
See original GitHub issueBootstrap v4.3.1
When navigating on dropdown using keyboard and if there are hidden(display: none) dropdown item in between then keyboard navigation stops.
Issues seems from: _dataApiKeydownHandler method, it doesn’t skip hidden element, it directly set focus on next element while next element can be hidden and focus does not set on hidden element and navigation gets broken.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
jquery select dropdown ignores keydown event when it's ...
preventDefault(); } });. It works fine for everything except when a select field dropdown list is opened, this event is ignored and a...
Read more >Keyboard accessible dropdown in Elm - DEV Community
In order to navigate the options list with up/down arrows, we need to keep track of the currently focused item. We also need...
Read more >Drop Down List inside Grid, custom navigation - Telerik
I have implemented custom navigation in the grid that works very well for text box inputs. However, it does not work well when...
Read more >.keydown() | jQuery API Documentation
The keydown event is sent to an element when the user presses a key on the keyboard. ... it is useful to attach...
Read more >How to Handle Alerts/Popups in Selenium WebDriver
hi shruthi,it is a great tutorial.thanque. i cannot see keyPress methods after clicking robot object . (dot)in eclipse.I imported java.awt.*.
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

Yup. The PR that was merged didn’t properly mention the issue hence why it remained open. I usually edit PR descriptions myself when they are wrong.
Good news, Thanks @jeremyvii for the fix