Closed
Bug 1785958
Opened 10 months ago
Closed 10 months ago
[CTW] RemoteAccessibles in background tabs should expose the offscreen state
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
106 Branch
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: Jamie, Assigned: morgan)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ctw-m3])
Attachments
(1 file)
When a tab is in the background, all RemoteAccessibles in that tab (including the descendants of any iframes) should get the offscreen state. We already handle this for LocalAccessibles.
Note that it's important to distinguish between focused and foreground/active here. A tab that isn't focused might still be in the foreground; e.g. if focus is in the address bar while a tab is still visible.
BrowsingContext::IsActive might be useful, though I'm not sure whether that propagates up/down the BrowsingContext tree for iframes. Looking at the code briefly, it does seem to walk ancestors, which is promising.
Practical impact: When CTW is enabled, live regions in background tabs are reported by NVDA when they shouldn't be.
Assignee | ||
Comment 1•10 months ago
|
||
Pushed by mreschenberg@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1d0e90b9f7d6 Set offscreen state based on BrowsingContext::IsActive r=Jamie
Comment 3•10 months ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 10 months ago
status-firefox106:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•