MDN may have intermittent access issues April 18 13:00 - April 19 01:00 UTC. See whistlepig.mozilla.org for all notifications.

mozilla

Compare Revisions

Compatibility with Legacy Addons

Change Revisions

Revision 642075:

Revision 642075 by billmccloskey on

Revision 642367:

Revision 642367 by billmccloskey on

Title:
Compatibility with Legacy Addons
Compatibility with Legacy Addons
Slug:
User:billmccloskey/e10s/Compatibility_with_Legacy_Addons
User:billmccloskey/e10s/Compatibility_with_Legacy_Addons
Content:

Revision 642075
Revision 642367
n26    <h3>n26    <h3 id="Cross-process_object_wrappers_(CPOWs)">
n68    <h4>n68    <h4 id="Bidirectional_CPOWs">
n91    <h4>n91    <h4 id="CPOWs_and_lifetimes">
tt106    <h3>
107      API emulation
108    </h3>
109    <p>
110      CPOWs are only one aspect of the emulation layer that multi
 >process Firefox uses to look like single-process Firefox. To see 
 >why CPOWs aren't enough, consider this add-on code:
111    </p>
112    <pre>
113<code>Services.obs.addObserver("<span class="st">content-document
 >-global-created</span>", function() { ... });</code>
114</pre>
115    <p>
116      This observer is supposed to run whenever a new content doc
 >ument is created. It won't work with multiple processes because t
 >he observer will fire in the content process, where the document 
 >is created; the add-on only registered the observer in the main p
 >rocess. For efficiency, Firefox doesn't normally propagate observ
 >er notifications between processes.
117    </p>
118    <p>
119      However, if an add-on doesn't specify the multiprocessCompa
 >tible flag in install.rdf, then any observers it adds will be reg
 >istered in the content process. Whenever one of these observers i
 >s notified, a synchronous message is sent to the main process not
 >ifying it. The observer registered by the add-on runs in the pare
 >nt.
120    </p>

Back to History