Closed
Bug 1841941
Opened 1 year ago
Closed 1 year ago
Use CreateStdAccessibleObject instead of AccessibleObjectFromWindow
Categories
(Core :: Disability Access APIs, task)
Tracking
()
RESOLVED
FIXED
117 Branch
| Tracking | Status | |
|---|---|---|
| firefox117 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
In several places, we use AccessibleObjectFromWindow to get a system generated IAccessible for the window. While this works well enough, it sends WM_GETOBJECT to our window, goes through our window proc, etc., which is pointless. We should just call CreateStdAccessibleObject directly instead, which is what the existing code ends up doing indirectly.
|
Assignee | |
Comment 1•1 year ago
|
||
We use AccessibleObjectFromWindow to get a system generated IAccessible for the window.
While this works well enough, it first sends WM_GETOBJECT to our window, goes through our window proc, etc., which is pointless since it will return nothing.
We should just call CreateStdAccessibleObject directly instead, which is what the existing code ends up doing indirectly.
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/799309422d5f
Use CreateStdAccessibleObject instead of AccessibleObjectFromWindow when getting the window IAccessible. r=nlapre
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox117:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•