FocusedChild fails when focus is in iframe
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
(Whiteboard: [mac2020_2])
Attachments
(1 file)
Given the following url, with focus on the input
data:text/html,<iframe src="data:text/html,<input>"></iframe>
We get the following results, depending on process topography when calling FocusedChild on the top level doc:
- Non-e10s: We get the input accessible.
- e10s: We get null because the unique id passed back in
RecvFocusChild
won't resolve in the sendingDocAccessibleParent
since it is a member of a child doc. - fission: We get null because no focused accessible is returned by the focus manager when focus is in a child doc.
We need to make all of these cases work like the non-e10s case.
A note about FocusedChild
: For some archaic reason accessibles are expected to return a direct focused child, or null. Document accessibles (including child docs) return a focused descendant. This API design choice is out of the scope of this bug.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Backed out changeset 4572c1ba670a (bug 1688972) for Browser-chrome failures in accessible/tests/browser/fission/browser_take_focus.js. CLOSED TREE
Log:
https://treeherder.mozilla.org/logviewer?job_id=328247553&repo=autoland&lineNumber=3502
Push with failures:
https://treeherder.mozilla.org/jobs?repo=autoland&group_state=expanded&selectedTaskRun=M-ic0V78TfCZw83t6Xmg3Q.0&revision=4572c1ba670a3ddb159cf37ba9684fb6055f260e
Backout:
https://hg.mozilla.org/integration/autoland/rev/6b095a7cc6c6d7718adf0d3e6b7b31bef96441cc
Comment 7•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Assignee | ||
Updated•2 years ago
|
Description
•