Confirm
1,982
edits
Changes
→Contributing
** Please check the open bugs for duplicates before filing a new bug.
* Link to file new e10s bug: http://is.gd/aTza8A
** Please include add the string "tracking-e10s" in the bug summary :? flag so we can more easily track your bug.
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
