W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: Synchronous XMLHttpRequest and events

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Fri, 13 May 2011 23:54:37 +0300
Message-ID: <4DCD9A8D.4000107@helsinki.fi>
To: Jonas Sicking <jonas@sicking.cc>
CC: Boris Zbarsky <bzbarsky@mit.edu>, public-webapps@w3.org
On 05/13/2011 11:39 PM, Jonas Sicking wrote:
> On Fri, May 13, 2011 at 1:21 PM, Boris Zbarsky<bzbarsky@mit.edu>  wrote:
>> On 5/13/11 4:07 PM, Jonas Sicking wrote:
>>> It *does* however call for a readystatechange event to be fired in
>>> response to the call to .open. Even if the request being started is a
>>> synchronous one.
>>> What is the use case for this event? It seems pretty useless and
>>> inconsistent to me.
>> I believe web pages depend on this to some extent; the fact that Gecko used
>> to not fire it caused all sorts of compat issues.  See
>> https://bugzilla.mozilla.org/show_bug.cgi?id=313646
> Ugh, yeah, in testing my patch I came across the same bug.
> So it appears the spec needs to be adjusted the other direction then.
> It needs to define that readystatechange needs to fire in all cases
> independent of the value of the asynchronous flag?

No. We don't want to fire any events *during* sync XHR processing.


> / Jonas
Received on Friday, 13 May 2011 20:55:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:19 UTC