Re: DOMWindowCreated not fired for some frames

2014-06-06 Thread Matthew Gertner
On Friday, June 6, 2014 6:49:55 PM UTC+2, Boris Zbarsky wrote: > That shouldn't be an issue. The cycle collector should handle it. Just > make sure you don't have a reference to that event handler on any > long-lived chrome objects. OK well I'm using beforescriptexecute and hopefully it should

Re: DOMWindowCreated not fired for some frames

2014-06-06 Thread Boris Zbarsky
On 6/6/14, 12:42 PM, Matthew Gertner wrote: On Friday, June 6, 2014 6:33:27 PM UTC+2, Boris Zbarsky wrote: The about:blank document is quite real, sadly... From what I'm seeing, the document object that ends up there (window.document) is not the same one as when DOMWindowCreated is fired.

Re: DOMWindowCreated not fired for some frames

2014-06-06 Thread Matthew Gertner
On Friday, June 6, 2014 6:33:27 PM UTC+2, Boris Zbarsky wrote: > The about:blank document is quite real, sadly... > > I'm not seeing anything obvious that gets fired when we reuse an inner > for a new document. At least nothing obvious in the window code. >From what I'm seeing, the document obj

Re: DOMWindowCreated not fired for some frames

2014-06-06 Thread Boris Zbarsky
On 6/6/14, 11:55 AM, Matthew Gertner wrote: So what's the best way to hook into the window so I am notified when the real document is created? The about:blank document is quite real, sadly... I'm not seeing anything obvious that gets fired when we reuse an inner for a new document. At least

Re: DOMWindowCreated not fired for some frames

2014-06-06 Thread Matthew Gertner
On Friday, June 6, 2014 4:28:35 PM UTC+2, Boris Zbarsky wrote: > On 6/6/14, 10:00 AM, Matthew Gertner wrote: > It's by design: when you ask for a window and we haven't actually > created one yet (because this is a new subframe that's doing its initial > load, say), we have to go ahead and create

Re: DOMWindowCreated not fired for some frames

2014-06-06 Thread Boris Zbarsky
On 6/6/14, 10:00 AM, Matthew Gertner wrote: Is this a Firefox bug or somehow by design? It's by design: when you ask for a window and we haven't actually created one yet (because this is a new subframe that's doing its initial load, say), we have to go ahead and create an about:blank one to r

Re: DOMWindowCreated not fired for some frames

2014-06-06 Thread Matthew Gertner
On Tuesday, March 25, 2014 7:34:27 PM UTC+1, Boris Zbarsky wrote: > Is the url about:blank when the window is created, perhaps? It's hard > to say without knowing exactly what you're logging/measuring. I spent some more time looking into this. The problem is apparently that we are observing htt

Re: DOMWindowCreated not fired for some frames

2014-03-26 Thread Matthew Gertner
On Tuesday, March 25, 2014 7:34:27 PM UTC+1, Boris Zbarsky wrote: > Is the url about:blank when the window is created, perhaps? It's hard > to say without knowing exactly what you're logging/measuring. Well I tried attaching a readyStateChange listener to every window so I could see if the real

Re: DOMWindowCreated not fired for some frames

2014-03-25 Thread Boris Zbarsky
On 3/25/14 2:22 PM, Matthew Gertner wrote: Is this a bug or am I misunderstanding something about the way the "DOMWindowCreated" event works? Is the url about:blank when the window is created, perhaps? It's hard to say without knowing exactly what you're logging/measuring. -Boris _