Skip to content

Platform Table: Keyboard Navigation Not Working in "Hiding Columns Depending on Table Size" Example #13174

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

Open
InnaAtanasova opened this issue Apr 2, 2025 · 1 comment
Assignees
Labels

Comments

@InnaAtanasova
Copy link
Contributor

In the Table example: Hiding columns depending on the table size, keyboard navigation is not functioning correctly.

Steps to Reproduce:

Tab to focus on the first row of the table.

Attempt to navigate to other rows using the arrow keys or Tab.

Expected Behavior:

Arrow keys should allow navigation between rows.

Tab should move focus within the table instead of leaving it.

Actual Behavior:

Arrow keys do not navigate to other rows.

Pressing Tab moves focus out of the table.

@mikerodonnell89
Copy link
Member

I think the best way to fix this would be a rework of how we're rendering the pop-in information. Currently we have it set up so that each row is actually two <tr>'s, where a second <tr> contains this secondary pop-in information and we're using some aria magic to have the screenreader treat the two adjacent <tr>'s as one row.

Image

I can't recall why we chose to do this but maybe it was to preserve the templating for the primary row. This issue is one of many side effects of this decision. In my opinion we should create a new template that is just 1 <tr> per row and use <div>s to break up the information within that row

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

No branches or pull requests

3 participants