Use aria-notify instead of A11yUtils.announce for UrlbarView's "special" announcements
Categories
(Firefox :: Address Bar, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | fixed |
People
(Reporter: Gijs, Assigned: dao)
References
(Blocks 1 open bug)
Details
(Keywords: access, Whiteboard: [sng][mcab-hnt])
Attachments
(1 file)
This is probably important for multi-context address-bar, as right now the code relies on being in a parent process where it can invoke the toplevel browser window's A11yUtils.announce. See bug 2016758 where this came up (and where I'm adding a temporary fix for now to unblock smart window).
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 1•2 months ago
|
||
(In reply to :Gijs (he/him) from comment #0)
This is probably important for multi-context address-bar, as right now the code relies on being in a parent process where it can invoke the toplevel browser window's
A11yUtils.announce.
Agreed. Thanks for filing this!
Updated•2 months ago
|
Comment 2•2 months ago
|
||
ariaNotify is riding the trains with 150, so you should be good to use it now.
When this does happen, please call ariaNotify on the most specific element. Based on a direct conversion from A11yUtils.announce, one would be forgiven if they just called document.ariaNotify, but while that will work, being able to identify the specific element whence a notification came is potentially useful for clients. This should also be explicitly tested with both NVDA and VoiceOver, since ariaNotify is new enough that there could be unforeseen issues (though I don't anticipate any).
| Assignee | ||
Comment 3•2 months ago
|
||
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 4•2 months ago
|
||
Hey Rares, I'm having trouble manually testing my patch. I see you've verified bug 2016758; would you mind sharing your steps so I can verify everything keeps working as expected?
Comment 5•2 months ago
|
||
Hi Dao, the A11yUtils error kept showing up every time I would Type G in the Smart bar in Smart Window with google as the search engine, or if I changed the search engine in preferences to Bing and then I would type bi in the smart bar. In our latest builds that error now longer shows up when we do that. Im not sure what this issue is about.
Updated•2 months ago
|
Updated•2 months ago
|
Description
•