On Sunday, February 24, 2013 4:27:16 AM UTC+1, Brian Smith wrote: > I notice that your company has developed a cross-browser framework for > building extensions. That means you are probably familiar with Chromium's > requirements here. I believe that Chromium requires you to do things the same > way as the Firefox Addon SDK recommends. (I'm not sure if that helps explain > my suggestion or not.)
Exactly, we need to emulate Chrome's behavior in the background window (see http://developer.chrome.com/extensions/xhr.html). Specifically we need to be able to make cross-domain requests in the background window and requests to chrome:// and resource:// URLs. I've implemented the background window as a hidden XUL window with a <browser> embedded. Looking over my code before the switch from FF18 to FF19, I wasn't actually doing anything at all except setting the type attribute of the <browser> to chrome (i.e. the default). Unfortunately I'm relying on DOMWindowCreated to inject my symbols into the window, and this is no longer fired in FF19 with the type set to chrome. I guess I'll file a bug about this. I was naively looking for a quick fix by injecting my own XHR implementation but it looks like that's problematic as I described in my OP. I'll see if I can use the content-document-global-created notification or something. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
