I believe bz's theory is that the <browser>'s binding was being force-applied because the <browser> was being wrapped to be passed to your JS-implemented content policy (as aContext). XBL bindings are force-applied when an element in a document is JS-wrapped and its binding hasn't yet been applied through normal mechanisms (i.e. layout).
Gavin On Sat, May 11, 2013 at 5:29 AM, Matthew Gertner <matt...@salsitasoft.com> wrote: > On Friday, May 10, 2013 6:15:59 PM UTC+2, Boris Zbarsky wrote: >> Is your policy being called with the subject set to the <browser>? > > Just before the error occurs, the policy is called with aRequestOrigin set to > chrome://browser/content/browser.xul and aContentLocation set to about:blank. > I just don't understand why the existence of the policy causes the <browser> > to be instantiated since as far as I can see CheckPolicy is called whether > the mPolicies list is empty or not. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
