Closed Bug 1210447 Opened 7 years ago Closed 7 years ago

e10s: Broken/missing accessibility subtree for pages with an iframe

Categories

(Core :: Disability Access APIs, defect)

Unspecified
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla44
Tracking Status
firefox44 --- fixed

People

(Reporter: jdiggs, Assigned: tbsaunde)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Steps to reproduce:
1. Launch Firefox with e10s enabled
2. Load: data:text/html,<iframe src="http://firefox.com"></iframe>
3. Launch Accerciser and drill down to the accessible associated with the iframe

Expected results: The accessible iframe would have a full subtree of descendant elements.

Actual results: The accessible iframe has a single descendant whose name displayed by Accerciser is "<dead>". If you use Accerciser's iPython console to get the childcount of the iframe, the return value is 1. But if you then ask for that child in the iPython console, the return value is None.

Impact: iframe content is not accessible when e10s is enabled.
Interestingly, this works as expected on Windows.
Comment on attachment 8668959 [details] [diff] [review]
fix ProxyAccessible::EmbeddedChildAt() on proxies of outerDocs

Review of attachment 8668959 [details] [diff] [review]:
-----------------------------------------------------------------

::: accessible/ipc/ProxyAccessible.cpp
@@ +1011,2 @@
>    uint64_t childID;
>    unused << mDoc->SendEmbeddedChildAt(mID, aChildIdx, &childID);

Unrelated to this bug: need to figure out caching this eventually.
Attachment #8668959 - Flags: review?(dbolter) → review+
https://hg.mozilla.org/mozilla-central/rev/196199146b8e
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla44
Assignee: nobody → tbsaunde+mozbugs
You need to log in before you can comment on or make changes to this bug.