On Monday, February 25, 2013 6:58:44 PM UTC+1, Boris Zbarsky wrote: > Depending on what you're doing, you could just be seeing the about:blank > inner window reused.
Specifically, I need to be able to inject properties into the window before any script is run. When I load with a chrome:// URL, DOMWindowCreated is fired so I can inject my stuff there. When I load from a resource:// URL or via my own protocol, it isn't fired. I tried adding properties to the window before the load (under the hypothesis that the inner window is being reused), but they don't seem to be there after the load. If the window is being reused, do I have any opportunity to inject my own properties? > I'm not clear on why the protocol handler would depend on > DOMWindowCreated.... See above. > You can set your channel's originalURI to whatever you want (which may > not match where the data is loaded from, which is the URI), right? So are you suggesting that I create the chrome:// URI channel myself and load from it after changing the originalURI? I could try that. If I can figure out a way to load using my own protocol handler then the problem goes away since I can make myprotocol://foo/bar point to the same location as chrome://foo/content/bar and the relative paths will resolve properly. Matt _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
