Closed
Bug 1394566
Opened 7 years ago
Closed 3 years ago
[a11y] AS: highlight context menu on tablet announces, "not checked" before items
Categories
(Firefox for Android Graveyard :: Activity Stream, defect, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mcomella, Unassigned)
References
Details
(Whiteboard: [mobileAS])
These aren't checkable items so they shouldn't announce any checked state. This ultimately doesn't affect functionality so I wouldn't say it should be prioritized over remaining work but it's annoying and potentially confusing.
Reporter | ||
Comment 1•7 years ago
|
||
Unfortunately, we're running short on time for 57 and may not have time for this one – it's annoying but we don't think it's worth blocking ship on.
Priority: -- → P3
Updated•7 years ago
|
tracking-fennec: ? → ---
Rank: 2
Reporter | ||
Updated•7 years ago
|
Blocks: as-android-talkback
Reporter | ||
Comment 2•7 years ago
|
||
All open Activity Stream bugs are moving from the whiteboard tag, "[mobileAS]", to the Firefox for Android component, "Activity Stream", so that I can keep better track of these bugs as the new triage owner; I will send out an email shortly with additional details, caveats, etc.
Component: Awesomescreen → Activity Stream
Comment 3•3 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•