W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

Re: [xhr] events for async requests

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 1 Feb 2010 04:26:46 -0800
Message-ID: <63df84f1002010426q46c7c549ub62c527d4f3f1d65@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: Ian Hickson <ian@hixie.ch>, Alexey Proskuryakov <ap@webkit.org>, WebApps WG <public-webapps@w3.org>
On Mon, Feb 1, 2010 at 4:12 AM, Anne van Kesteren <annevk@opera.com> wrote:
> On Mon, 01 Feb 2010 12:56:57 +0100, Jonas Sicking <jonas@sicking.cc> wrote:
>> On Mon, Feb 1, 2010 at 3:20 AM, Anne van Kesteren <annevk@opera.com>
>> wrote:
>>>> Can responseText ever be non-empty without being in the LOADING state?
>>>> I.e. do these to actions happen from the same, or from separate, tasks
>>>> posted to the event loop?
>>> The same.
>>> I could make this more explicit if you want.
>> Where in the spec is this defined? I guess my answer is yes, it'd be
>> nice if it was more explicit. :)
> You haven't even read the specification on this yet? :/
> See step 9 under the send() method:
>  http://dev.w3.org/2006/webapi/XMLHttpRequest-2/
> In particular the two sections flagged with "If the asynchronous flag is
> true".

I have read the spec, but I still don't see where it says that
responseText and the state is updated from the same task.

Is the idea that every bullet under "The same-origin request event
rules are as follows" is always performed from the same task? But even
then the actual updating of the state is not listed in the same set of

/ Jonas
Received on Monday, 1 February 2010 12:27:40 UTC

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