On 1/4/16 12:09 PM, Dave Townsend wrote:
On Mon, Jan 4, 2016 at 12:03 PM, Cameron Kaiser <ckai...@floodgap.com> wrote:
What's different about nsIProtocolHandler in e10s? OverbiteFF works in 45
aurora without e10s on, but fails to recognize the protocol it defines with
e10s enabled. There's no explanation of this in the browser console and
seemingly no error. Do I have to do extra work to register the protocol
handler component, or is there some other problem? A cursory search of MDN
was no help.
Assuming you are registering the protocol handler in chrome.manifest
it will only be registered in the parent process but you will probably
need to register it in the child process too and make it do something
sensible in each case. You'll have to do that with JS in a frame or
process script.
That makes sense, except I'm not sure how to split it apart. Are there
any examples of what such a parent-child protocol handler should look
like in a basic sense? The p-c goop in netwerk/protocol/ is not really
amenable to determining this, not least of which being written in C++.
Cameron Kaiser
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
