#18721 closed defect (fixed)
form/Select throws an error when it has 0 or 1 option and keyboard navigation is used
Reported by: | adros | Owned by: | bill |
---|---|---|---|
Priority: | undecided | Milestone: | 1.9 |
Component: | Dijit | Version: | 1.10.4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Method '_getNextFocusableChild' in _keyNavMixin may return null, which is case of Select with 0 or 1 option. But method '_keyboardSearch' is not ready for this and an error is raised from '_keyboardSearchCompare' method.
This can be simulated also in 'dijit/tests/form/test_Select.html', focus to 'Initial Empty' or 'Single Item' select, and press e.g. 'a' (while the dropdown is closed) and see errors in console.
I will create a pull request that fixes this issue.
Change History (4)
comment:1 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 Changed 6 years ago by
Milestone: | tbd → 1.9 |
---|
Note: See
TracTickets for help on using
tickets.
In cef0a828574cc9f9f80f8bce0a46b7f293630232/dijit: