Confirm
1,982
edits
Changes
→Common Issues
Basic browsing should work as expected. Tabs that are loaded remotely (i.e., in a separate process) will have their title underlined. By default, all tabs share just one content process. If one tab crashes, they all crash. Process-per-tab, like Google Chrome, is on our roadmap.
=== Accessibility Support ===
Currently we have basic support for accessibility with e10s however, there is a great deal of work left to finish. Accessibility clients require direct access to information about content, which in non-e10s was queried directly using sync calls into the DOM. These calls generally came in on the main UI thread of the application and expect a response on return. With e10s, chrome generally communicates with content through asynchronous interfaces. This is incompatible with current clients. As such the Accessibility team is currently working on a two phase approach to getting accessibility working under e10s:
* Initial support with sync chrome -> content calls for most common apis, with light weight caching to cut down on the heaviest api traffic.
* A black list of clients known to have issues with e10s will be added. When a blacklisted client is detected Firefox will prompt the user to disable e10s and restart.
* Gradual improvement using chrome side caching of DOM state, working toward a mostly asynchronous interface.
* Eventual removal of the blacklist once we are ready to drop support for non-e10s.
{{bug|1029143}}
=== Common Issues ===
