Closed
Bug 1784841
Opened 2 years ago
Closed 2 years ago
[CTW] Platforms don't use unified OffsetAtPoint (AKA OffsetAtPoint doesn't support cached RemoteAccessible on Windows)
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
105 Branch
| Tracking | Status | |
|---|---|---|
| firefox105 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ctw-m2])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
I discovered this while I was verifying real world test cases for ctw-m2.
Bug 1775329 unifies OffsetAtPoint and implements support for cached RemoteAccessible. However, the platform specific code doesn't use this unified method.
On non-Windows, this isn't a problem because we just have a pointless conditional for local and remote; we still do the right thing. However, on Windows, the code was local only, so this just returns failure for cached remote.
|
Assignee | |
Comment 1•2 years ago
|
||
Most importantly, this means OffsetAtPoint is now supported for cached RemoteAccessible on Windows.
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e649496f940b
Use unified OffsetAtPoint in platform specific code. r=morgan
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox105:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 105 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•