On Saturday, May 11, 2013 7:37:00 PM UTC+2, Gavin Sharp wrote: > 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).
That makes sense. So is it a bug that this causes an error to be logged in the Error Console? It seems to me that I should be allowed to register a content policy at startup (before the first browser window is loaded) without getting error messages. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
