Skip to content
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

Fix a bug with keyboard navigation when there is no data #1424

Merged
merged 1 commit into from
Sep 5, 2019

Conversation

nmfriesen
Copy link
Contributor

When Keyboard.js is mixed into a grid and the grid does not have any data, when the grid gets focus, using the up or down arrow keys, or the Page Up or Page Down buttons will cause an error and log it in the console window. I've created an example of this here: http://plnkr.co/edit/iI2TuSy5HnrhSmEqulED (open the F12 console to see the errors).

This should fix the issue by not trying to navigate if no node is focused.

…ns would cause an error on a grid with no data
@edhager edhager merged commit 467160e into dojo:master Sep 5, 2019
msssk pushed a commit that referenced this pull request Apr 18, 2020
…ns would cause an error on a grid with no data (#1424)
msssk pushed a commit that referenced this pull request Apr 18, 2020
…ns would cause an error on a grid with no data (#1424)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants