Changes

For developers interested in helping out, MDN has a [https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox good introduction to e10s], useful for both Firefox and add-on developers.

Generally the browser should be stable and usable, without major issues or crashes. Profiles that have lots of older addons will likely experience slowness or other issues. If you run into any trouble, start diagnosing by disabling addons and testing again.

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. This is incompatible with current a11y clients. As such the Accessibility Team is currently working on a two phase approach to getting accessibility working under e10s:

* {{bug|1029143}} - Implement accessibility for sandboxed e10s

Add-on authors should refer to the MDN [https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox Firefox Add-on Migration Guide] documentation for porting existing add-ons to e10s. Also see the [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox Multiprocess Firefox] documentation for design information.