Boris Zbarsky wrote:
> John J. Barton wrote:
>> stream = channel.open();
>
> For some channels this won't return until there is data to read from the
> stream, so in the case of, say, an HTTP channel this will indeed process
> events before returning.
>
> This has been the case ever since open() became supported for all
> built-in channels, though... So since 2003 or so. See
> http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/netwerk/base/public/nsNetUtil.h&rev=1.106&mark=570-571#559
>
>
>
> Not sure about changes, though. But the whole event system has changed,
> so depending on where events are coming from and what else is going on,
> you might get slightly different event sequencing.
>
> -Boris
>
Just in case someone comes this way, the change that really bit me was
that window.location = "javascript:..." is now asynchronous. This threw
Firebug off, creating errors that appeared in my traces after open()
blocked. So I focused on the "source" of the errors as open(). I suppose
I will have to start marking my traces by thread.
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
