Make xpcAccessible::GetDeepestChildAtPoint walk into remote child documents
Categories
(Core :: Disability Access APIs, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox76 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Currently, it stops at an OuterDocAccessible. It will need to walk into that and continue the search.
|
Assignee | |
Comment 1•5 years ago
|
||
Yura, is this going to break the Dev Tools A11y Panel? The crash worked around in bug 1568163 suggests the A11y Panel might ask for this when running within the Browser Toolbox. With the change proposed here, instead of stopping at the OuterDoc (XUL browser), it will return a ProxyAccessible within a remote document.
If this is problematic, we could just make the tests hit test on the root (which will return the OuterDoc), then hit test on the returned OuterDoc.
|
||
Comment 2•5 years ago
|
||
It might be currently, though I think with fission it might be OK since we are relying on DOM events to trigger the code that runs getDeepestChildAtPoint in the right process.
|
|
Assignee | |
Comment 3•5 years ago
|
||
Previously, it stopped at an OuterDocAccessible.
Now, if an OuterDocAccessible is encountered, it continues the search in the remote child document.
As part of this, the bulk of the code has been moved into AccessibleOrProxy, since other callers might find this useful in future.
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
||
Comment 5•5 years ago
|
||
| bugherder | ||
|
|
Assignee | |
Updated•5 years ago
|
Description
•