Electrolysis/Accessibility: Difference between revisions
Jump to navigation
Jump to search
m (header) |
m (link) |
||
| Line 3: | Line 3: | ||
Accessibility clients require direct access to information about content. In non-e10s this information is queried directly using sync calls into the DOM. These calls generally arrive on the application main or UI thread and expect a response on return. With e10s, the chrome process generally communicates with content through asynchronous interfaces which is incompatible with current accessibility clients. As such the e10s and Accessibility Teams are working on a new approaches for accessibility clients. | Accessibility clients require direct access to information about content. In non-e10s this information is queried directly using sync calls into the DOM. These calls generally arrive on the application main or UI thread and expect a response on return. With e10s, the chrome process generally communicates with content through asynchronous interfaces which is incompatible with current accessibility clients. As such the e10s and Accessibility Teams are working on a new approaches for accessibility clients. | ||
Currently electrolysis is blocked from running on Windows and OSX if recent accessibility use is detected. | |||
* [http://mxr.mozilla.org/mozilla-central/search?string=MultiprocessBlockPolicy%28%29 Embedded platform code] that handles e10s blocking. | |||
= Windows = | = Windows = | ||
Revision as of 15:38, 1 June 2016
Overview
Accessibility clients require direct access to information about content. In non-e10s this information is queried directly using sync calls into the DOM. These calls generally arrive on the application main or UI thread and expect a response on return. With e10s, the chrome process generally communicates with content through asynchronous interfaces which is incompatible with current accessibility clients. As such the e10s and Accessibility Teams are working on a new approaches for accessibility clients.
Currently electrolysis is blocked from running on Windows and OSX if recent accessibility use is detected.
- Embedded platform code that handles e10s blocking.
Windows
Tracking List - tbd
See the Windows e10s Accessibility wiki page for support implementation detail.
OSX and Linux
- Sync chrome -> content calls for most common apis, with light weight caching to cut down on the heaviest api traffic.
- Gradual improvement using chrome side caching of DOM state, working toward a mostly asynchronous interface.