OSX VoiceOver cursor does not respond to tab key press with e10s
Categories
(Core :: Disability Access APIs, defect, P3)
Tracking
()
People
(Reporter: umer.farooq, Unassigned)
References
Details
(Keywords: multiprocess, regression, Whiteboard: [tpi:+][mac2020_1])
Updated•8 years ago
|
Comment 1•8 years ago
|
||
Comment 3•8 years ago
|
||
Updated•8 years ago
|
![]() |
||
Updated•8 years ago
|
![]() |
||
Comment 4•8 years ago
|
||
Comment 5•8 years ago
|
||
Updated•6 years ago
|
Comment 7•6 years ago
|
||
Morgan, is this actually still valid? I just tabbed through a few pages with VoiceOver on, and VoiceOver cursor was always where the focused item was, e. g. I could press tab a few times in Bugzilla or on mozilla.org, and when I then navigated with CTRL+Option+RightArrow, I continued from where focus was, so VoiceOver cursor was following. This may have been fixed by one of the other bugs. Can you confirm? Also NI'ing Marius to see if he can still reproduce with a current Nightly build on Catalina or Mojave.
Comment 8•6 years ago
•
|
||
WFM, but I think Eitan mentioned to me moderately recently that he was having issues with this behaviour being consistent (or maybe the issue was VO wouldn't focus the web area consistently, like safari? I'm not sure... ni?'ing him here).
Comment 9•6 years ago
|
||
Hi Marco, I have tested this issue and it seems that it is no longer reproducible on the latest Firefox Nightly (76.0a1 Build ID - 20200317214918) and latest Firefox Beta (75.0b4 Build ID - 20200317211402). Now, the VoiceOver follows the focus and recognize the links.
However, I have managed to reproduce the issue on the latest Firefox Release (74.0 Build ID - 20200309095159) using the steps from the description.
Considering the above, using the mozregression tool I have managed to find the fix. Here is the pushlog:
First good revision: 14a1863166fca4a218a687cf04a750577b1c567a
Last bad revision: 96695fc2f0f257540907d87ec2d0479bc422fd76
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=96695fc2f0f257540907d87ec2d0479bc422fd76&tochange=14a1863166fca4a218a687cf04a750577b1c567a
From the pushlog, it seems that Bug 1617301 has fixed this issue.
I hope it helps :).
Comment 10•6 years ago
|
||
Thank you for the investigation and verification, Marius! Closing as FIXED and linking to the actual fixing bug.
Comment 11•6 years ago
|
||
Verified as per comment #9.
Comment 12•6 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Updated•6 years ago
|
Description
•