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).
But the original error was that the webNavigation was null... so what's
loading the about:blank in the first place?
--
Warning: May contain traces of nuts.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
