On Monday, February 25, 2013 8:40:45 PM UTC+1, Boris Zbarsky wrote: > On 2/25/13 1:46 PM, [email protected] wrote: > > So are you suggesting that I create the chrome:// URI channel myself and > > load from it after changing the originalURI? > > Yes, I think so.
I couldn't see a way to load the document via the channel. nsDocShell::LoadURI() does an awful lot. However, I took a peek at the source and noticed http://mxr.mozilla.org/mozilla-central/source/dom/base/nsGlobalWindow.cpp#2378. It looks like in a chrome docshell Firefox wants the document to have the system principal or it doesn't fire DOMWindowCreated. I added URI_INHERITS_SECURITY_CONTEXT to my protocolFlags and now it works. Based on the comment above the nsGlobalWindow code, this looks like a bug to me since it is catching cases other than the about:blank situation it appears to be designed for. Shall I file a bug or do you think this behavior is intended? Matt _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
