You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using VoiceOver to navigate within a table that has custom React Aria-based keyboard navigation, there is a noticeable delay in cell announcements.
For example, in a 3x3 table:
Moving from Row 2, Cell 2 → Row 2, Cell 1 → Row 2, Cell 2,
VO might get stuck announcing Row 2, Cell 1, instead of updating to Row 2, Cell 2 if you're fast enough.
🤔 Expected Behavior?
VO should announce the actual focused cell
😯 Current Behavior
If change happened fast enough VO announces previous cell.
@snowystinger I've noticed that using keyboard rerenders the whole table (you can use react-devtools and enable the "Highlight updates when components rerender".
It seems that the table component suffers from unnecessary renders due to the Focus manager state. Noticed that in large virtualized tables it's possible to experience degraded performance too 😢. I was looking for any potential solution for this, and wondering if it's a separate issue to take a look at.
Provide a general summary of the issue here
When using VoiceOver to navigate within a table that has custom React Aria-based keyboard navigation, there is a noticeable delay in cell announcements.
For example, in a 3x3 table:
Moving from Row 2, Cell 2 → Row 2, Cell 1 → Row 2, Cell 2,
VO might get stuck announcing Row 2, Cell 1, instead of updating to Row 2, Cell 2 if you're fast enough.
🤔 Expected Behavior?
VO should announce the actual focused cell
😯 Current Behavior
If change happened fast enough VO announces previous cell.
💁 Possible Solution
No response
🔦 Context
No response
🖥️ Steps to Reproduce
Version
1.4.1
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
MacOS - 15.2 (24C101)
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered: