Re: PSA: inbound/central/birch closed

2013-05-11 Thread L. David Baron
On Saturday 2013-05-11 20:46 -0400, Ehsan Akhgari wrote: > I tried backing out everything that looked suspicious on the birch side of > the merge but the leaks continued to persist. Not sure what to do next, > and I won't be around for further investigation today. The trees remain > closed for no

Re: PSA: inbound/central/birch closed

2013-05-11 Thread Ehsan Akhgari
I tried backing out everything that looked suspicious on the birch side of the merge but the leaks continued to persist. Not sure what to do next, and I won't be around for further investigation today. The trees remain closed for now. -- Ehsan On Sat, May 11, 2013 at

Re: Error on startup when registering content policy from bootstrapped extension

2013-05-11 Thread Neil
Gavin Sharp wrote: I believe bz's theory is that the 's binding was being force-applied because the 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 firs

PSA: inbound/central/birch closed

2013-05-11 Thread Ehsan Akhgari
The latest merge from m-c to inbound resulted in all debug unit tests going orange. This is caused by bad interaction of things that are landed on birch and inbound. I've closed birch/inbound/central until this issue is resolved in order to prevent further damage. I've tried backing out bug 8683

Re: Error on startup when registering content policy from bootstrapped extension

2013-05-11 Thread Matthew Gertner
https://bugzilla.mozilla.org/show_bug.cgi?id=871176 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Error on startup when registering content policy from bootstrapped extension

2013-05-11 Thread Gavin Sharp
I suppose you could say it's a bug in the browser binding. Worth filing, CC me? Gavin On Sat, May 11, 2013 at 2:26 PM, Matthew Gertner wrote: > On Saturday, May 11, 2013 7:37:00 PM UTC+2, Gavin Sharp wrote: >> I believe bz's theory is that the 's binding was being >> force-applied because the w

Re: Error on startup when registering content policy from bootstrapped extension

2013-05-11 Thread Matthew Gertner
On Saturday, May 11, 2013 7:37:00 PM UTC+2, Gavin Sharp wrote: > I believe bz's theory is that the 's binding was being > force-applied because the 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 i

Re: Error on startup when registering content policy from bootstrapped extension

2013-05-11 Thread Gavin Sharp
I believe bz's theory is that the 's binding was being force-applied because the 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 mec

Re: Error on startup when registering content policy from bootstrapped extension

2013-05-11 Thread Matthew Gertner
On Saturday, May 11, 2013 11:29:58 AM UTC+2, Matthew Gertner wrote: > 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

Re: Error on startup when registering content policy from bootstrapped extension

2013-05-11 Thread Matthew Gertner
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 ? 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 unde