-
Notifications
You must be signed in to change notification settings - Fork 6.7k
keyboard-nav directive for dropdown menu throws error when using up arrow first #4327
Comments
This is fixed in master. |
Installed the master, which resolved to angular-bootstrap#0b83ef6828, and the problem persists. |
Crud. Yea, this is a bug. You can reproduce via this plunker which was used to fix #4091. |
Hang on. That plunker is not using the latest code. I fixed #4091 and there were at least three issues. I need to test again w/ the latest code. |
Yea, this is a bug. Here's an updated plunker. The problem is that |
* add support for when user opens dropdown and then presses the up arrow key. Fixes angular-ui#4327
* add support for when user opens dropdown and then presses the up arrow key. Fixes angular-ui#4327
Thank you for your quick response time fixing this bug |
You're welcome. Just a note that ARIA does not specifically state that for menus, the up arrow should wrap and select the bottom (which is weird because it does for other widges - I saw at least accordion and radio groups). That said, as I play with a menu on my Mac, it does wrap - which I think is the right use case. |
When you click on a drop down menu and hit the up arrow the following error is thrown. Uncaught TypeError: Cannot read property 'focus' of undefined
If you hit down first and then up it is not an issue
The text was updated successfully, but these errors were encountered: