At least for <xul:browser> where remote="true", we behave as you describe; namely, we use the "remote-browser" binding defined in toolkit/content/widgets/remote-browser.xml, which on construction, injects a "browser-child.js" frame script via the message manager.
On 29/07/2014 4:58 AM, Neil wrote: > How do toolkit components in content processes start themselves up, does > it all have to be done through content scripts loaded by the message > manager? > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
