Closed
Bug 1768726
Opened 2 years ago
Closed 2 years ago
Make RemoteAccessibleBase::BoundsWithOffset thread safe for Android
Categories
(Core :: Disability Access APIs, task)
Tracking
()
RESOLVED
FIXED
102 Branch
Tracking | Status | |
---|---|---|
firefox102 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
(Whiteboard: [ctw-m1])
Attachments
(1 file)
In Android we need to keep the remote accessible methods thread safe. That means no direct references to local accessibles, or anything DOM or layout.
We have the advantage of always being remote except for a 0 offset browser element, and no support for full page zoom.
Assignee | ||
Comment 1•2 years ago
|
||
In Android we need to keep the remote accessible methods thread safe. That means no direct references to local accessibles, or anything DOM or layout.
We have the advantage of always being remote except for a 0 offset browser element, and no support for full page zoom.
Also removed the visual/layout viewport offset in the bounds method since
the top level doc will always have its visual and layout viewport match.
Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fabb66e86d29 Make RemoteAccessibleBase::BoundsWithOffset thread safe for Android. r=morgan
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox102:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•