a11y: 'tab' stops scrolling through `Table` with `onRowClick`
See original GitHub issueSeems like accessibility is broken in Table
and maybe other components (I haven’t tried).
First case: it happens if I press ‘Shift-Tab’ so it moves the scroll bar up as you can see on the next image. After that the last item is the last visible item, because it then switches focus to a button:
Second case if I press ‘Up Arrow’ key in a way that partially or fully hides focused item:
You can find this table on codepen: http://codepen.io/dattaya/full/evrYqM/
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
tabulator performs unwanted scrolling on row click
I found the source of the unwanted scroll-to-top. I was performing a table.setData() during componentDidUpdate(). Once the table.
Read more >How-to: Use the tabindex attribute - The A11Y Project
tabindex is a global attribute that allows an HTML element to receive focus. It needs a value of zero or a negative number...
Read more >onRowClick - Row Click Script - HCL Product Documentation
Activates an event handler when a pointer control clicks a row in a control.
Read more >Data Grid - Events - MUI X
You can subscribe to the events emitted by the data grid to trigger custom behavior. ... event using the onRowClick prop—try it out...
Read more >Table - Ant Design
A table displays rows of data. ... effective for all columns when set on table props. ... The sum of unfixed columns should...
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 FreeTop 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
Top GitHub Comments
Default behavior has been fixed/corrected via e6656c1. It will go out with the next point release.
Thanks for the follow-up info!
I’m going to leave it open for now and give it some more thought. I think maybe I can improve this by default without impacting perf too much.