Rotor doesn't return results when AXDirectionPrevious is used with no start element.
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
People
(Reporter: eeejay, Assigned: eeejay)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [mac2020_2])
Attachments
(1 file, 1 obsolete file)
STR:
- Load
data:text/html,<div><a href="a">one</a></div><div><a href="b">two</a></div><div><a href="c">three</a></div>
- Go to last item with VO next
- Press VO+Left
Result:
Cursor is unresponsive, after repeated presses it goes to the second link, and then it goes to the webarea
Expected:
VO cursor should go back to the second and first link respectively with each press of VO+left
It looks like a previous search that is done with no start element won't return any items.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Depends on D91875
Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/05c9cc6dd872 Support AXDirectionPrevious in rotor with no start element. r=morgan
Comment 3•3 years ago
|
||
Backed out for build bustage on MOXSearchInfo.mm.
Backout link: https://hg.mozilla.org/integration/autoland/rev/858ebc3918cf3d030caea262416d90bb5a26cec1
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=317343578&repo=autoland&lineNumber=10979
Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/80827b9f7918 Support AXDirectionPrevious in rotor with no start element. r=morgan
Comment 5•3 years ago
|
||
bugherder |
Assignee | ||
Comment 6•3 years ago
|
||
Depends on D92797
Assignee | ||
Comment 7•3 years ago
|
||
Comment on attachment 9180223 [details]
Bug 1668142 - Support AXDirectionPrevious in rotor with no start element. r=morgan!
Beta/Release Uplift Approval Request
- User impact if declined: VoiceOver users will have difficulty moving the cursor backwards on some sites
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: Bug 1668137, Bug 1668100
- Risk to taking this patch: Medium
- Why is the change risky/not risky? (and alternatives if risky): This isn't a small change, but it has tests and has been verified.
- String changes made/needed:
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 8•3 years ago
|
||
Is this a new issue? Nothing in this bug suggests it's a regression and given how late we are in the cycle I'm not sure it would qualify for uplift if not.
(same question as in bug 1668137)
Assignee | ||
Comment 9•3 years ago
|
||
Yes, this bug is regressed by bug 1657418.
Updated•3 years ago
|
Assignee | ||
Comment 10•3 years ago
|
||
Since it is late in the cycle, and VoiceOver support in mac is still experimental, I think it is fine if this is declined beta.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Description
•