Confirm
1,982
edits
Changes
updates to contrib
If your browser breaks in a way that you can't easily recover to change this setting, start Firefox in Safe Mode (by holding Alt/Option during start) which will force-disable e10s and allow you to enter the Preferences dialog and untick the checkbox.
==Contributing==
* The simplest way to help out is to test a release that has e10s enabled, and file bugs bug when you find them.Please try to find duplicates prior to filing.** The [[Electrolysis/Roadmap|project roadmap overview]] provides current bug lists slated for development based on a set of 2015 milestones.** The current incoming [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&o5=nowordssubstr&o9=equals&v10=needinfo&o2=equals&v5=meta&v9=%3F&o4=nowordssubstr&v2=---&v4=addon%2Cadd-on%2Cextension%2Cmeta&f10=flagtypes.name&f1=OP&v6=needinfo&o3=anywordssubstr&f8=OP&v3=e10s&resolution=---&o6=notsubstring&f9=cf_tracking_e10s&f4=short_desc&o10=notsubstring&query_format=advanced&f3=short_desc&f2=cf_tracking_e10s&f11=CP&f5=keywords&f6=flagtypes.name&f7=CP&list_id=11857722 e10s weekly triage bug list]** Link to file new e10s bug: http://is.gd/aTza8A
Most bugs in e10s occur because code in the chrome process tries to access data in a content process. All of the DOM objects for a XUL browser element, as well as its DocShell, live in the content process. Typical access paths are via <code>browser.contentWindow</code>, <code>browser.docShell</code>, or some variation of them. Often, these property accesses will generate errors in the console, which makes these bugs fairly easy to detect. MDN has a good introduction to e10s, useful for both Firefox and add-on developers: https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox
