Bug 1956150 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
We should fire UIA AsyncContentLoaded for EVENT_DOCUMENT_LOAD_COMPLETE. This alone doesn't seem to be enough to get Narrator to auto read the document (bug 1949921), but [this Chromium commit](https://github.com/chromium/chromium/commit/66842a429e085dc17eeab8172cb22c2ad950f6b8) suggests that this is at least part of the equation:

> This change fires UIA_AsyncContentLoaded as the UIA analogue to
IA2_EVENT_DOCUMENT_LOAD_COMPLETE. Narrator plans to use this to determine when to start auto-reading webpages.

We should support this event anyway, so let's get this landed here and add deal with other fixes separately.
Revision 1 by
on 
We should fire UIA AsyncContentLoaded for EVENT_DOCUMENT_LOAD_COMPLETE. This alone doesn't seem to be enough to get Narrator to auto read the document (bug 1949921), but [this Chromium commit](https://github.com/chromium/chromium/commit/66842a429e085dc17eeab8172cb22c2ad950f6b8) suggests that this is at least part of the equation:

> This change fires UIA_AsyncContentLoaded as the UIA analogue to IA2_EVENT_DOCUMENT_LOAD_COMPLETE. Narrator plans to use this to determine when to start auto-reading webpages.

We should support this event anyway, so let's get this landed here and add deal with other fixes separately.

Back to Bug 1956150 Comment 0