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 Modal is opened via TalkBack I am unable to change cursor position by swiping left or right. The cursor always comes back to the first focusable element. The flow works perfectly on VoiceOver (macOS).
🤔 Expected Behavior?
I should be able to navigate the elements inside Modal by swiping left or right.
where the activeElement is now returning the document body after the RAF instead of the newly focused input element after the swipe operation. Replacing this with e.relatedTarget seems to work just fine, I can't seem to reproduce the original issue in Firefox even with the updated change
The fix above actually breaks another use case of ours since we still do want to coerce focus back to the Modal if focus is genuinely lost to the body but there isn't a great to differentiate that any longer for Talkback it seems. I've filed a bug against Chrome via https://issuetracker.google.com/issues/384844019 to see if they can shed any light as to what may have changed as of late, currently digging to see if there are any alternative paths here.
Provide a general summary of the issue here
When Modal is opened via TalkBack I am unable to change cursor position by swiping left or right. The cursor always comes back to the first focusable element. The flow works perfectly on VoiceOver (macOS).
🤔 Expected Behavior?
I should be able to navigate the elements inside Modal by swiping left or right.
😯 Current Behavior
TalkBack cursor is blocked on the first element.
💁 Possible Solution
No response
🔦 Context
No response
🖥️ Steps to Reproduce
The bug is visible in Modal's documentation - https://react-spectrum.adobe.com/react-aria/Modal.html.
Version
1.5.0
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
Android 14. TalkBack 14.1, Chrome
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered: