Closed
Bug 1724192
Opened 4 years ago
Closed 4 years ago
[A11y] The browser crashes when using VoiceOver while focusing the address bar and pressing VO + Shift + Down
Categories
(Firefox :: Disability Access, defect, P1)
Tracking
()
RESOLVED
DUPLICATE
of bug 1724173
People
(Reporter: danibodea, Unassigned)
References
(Regression)
Details
(Keywords: access, regression)
Note
- When the user has VoiceOver activated and focuses the address bar and presses VO + Shift + Down (arrow key), he will notice that the browser will crash.
Affected versions
- Nightly v92.0a1
Affected platforms
- all
Steps to reproduce
- Start VoiceOver.
- Launch browser.
- Focus the address bar.
- VO + Shift + Down
Expected result
- The browser does not crash.
Actual result
- The browser crashes immediately.
- https://crash-stats.mozilla.org/report/index/bp-c201e553-8ec5-4c2f-8ead-7f47c0210805
Regression range
- Appears to be a regression. WIll come back with mozregression results.
Additional notes
- This issue does not occur with NVDA (Windows) or ORCA (Ubuntu).
Priority: -- → P1
I was able to reproduce this bug using MacOS 11 with latest firefox nightly v92.0a1
steps:
- turn voiceover on in macOS
- go to about:addons
- voiceover will start talking about each section automatically
- wait less than a minute
It will crash when it reaches "search.addons.mozilla.org, edit text" wich is the top right search field in about:Addons
Reporter | ||
Comment 2•4 years ago
|
||
Mozregression results:
Bug 1682865: Map roles::EDITCOMBOBOX to mozTextAccessible r=eeejay
Differential Revision: https://phabricator.services.mozilla.com/D101407
Has Regression Range: --- → yes
Has STR: --- → yes
status-firefox90:
--- → affected
status-firefox91:
--- → affected
status-firefox-esr78:
--- → unaffected
Regressed by: 1682865
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Updated•4 years ago
|
status-firefox90:
affected → ---
status-firefox91:
affected → ---
status-firefox92:
affected → ---
status-firefox-esr78:
unaffected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•