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

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Joanmarie Diggs]

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.

Comment 1

[James Teh [:Jamie]]

Interestingly, this works as expected on Windows.

Comment 2

[Trevor Saunders (:tbsaunde)]

Attachment: fix ProxyAccessible::EmbeddedChildAt() on proxies of outerDocs

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

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.

Comment 4

[Pulsebot]

https://hg.mozilla.org/integration/mozilla-inbound/rev/196199146b8e

Comment 5

[Phil Ringnalda (:philor)]

https://hg.mozilla.org/mozilla-central/rev/196199146b8e