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

Bug: v9 DataGrid resizable columns with keyboard sends focus to document.body #28244

Closed
smhigley opened this issue Jun 16, 2023 · 0 comments · Fixed by #28493
Closed

Bug: v9 DataGrid resizable columns with keyboard sends focus to document.body #28244

smhigley opened this issue Jun 16, 2023 · 0 comments · Fixed by #28493

Comments

@smhigley
Copy link
Contributor

Describe the issue:

After choosing "Keyboard Column Resizing" in the columnheader menu, keyboard focus moves back up to document.body (the default focus target when a focused element is removed without actively moving focus somewhere else). When it does so, both a screen reader user's cursor, and a magnification user's view would jump back up to the top of the document.

In addition to that, arrow keys resize the column no matter what element is currently in focus.

Expected behavior:

If we continue with this approach, focus should return to the columnheader that the menu was triggered from, and arrow keys should only resize the column when that specific columnheader is in focus.

In general, I think we should rethink the approach a bit -- there's no feedback on what's going on as you resize, or information on how to resize after choosing the menu item. My initial thought would be to both implement something like a keyboard shortcut (ctrl + brackets, for example) and a context menu that lists the keyboard shortcut and also has a way to directly input a new width as text. The latter would work for people who are not using the keyboard, but might have issues resizing with a mouse for any reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants