Re: [XHR] Event firing order. XMLHttpRequestUpload then XMLHttpRequest or reverse

Sorry for the delay.

On Tue, Sep 3, 2013 at 9:00 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Sep 3, 2013 at 9:18 AM, Takeshi Yoshino <tyoshino@google.com>
> wrote:
> > In the spec, we have three "cancel"s
> > - cancel an instance of fetch algorithm
> > - cancel network activity
>
> These are the same. Attempted to clarify.
>
>
Verified that the order of events are the same for abort() and abort error.

Thanks for factoring out termination algorithm. It's clearer now.


>
> > - cancel a request
>
> This is the end user terminate, correct?
>

Yes. So, this includes any kind of event resulting in termination of fetch
algorithm (network, termination by some user's instruction to UA)?


> Would you like to be
> acknowledged as "Takeshi Yoshino"? If you can give me your name in
> kanji I can include that too. See e.g.
> http://encoding.spec.whatwg.org/#acknowledgments for some examples.
>
>
Thank you. Just alphabetical name is fine.


> See http://xhr.spec.whatwg.org/ for the updated text. And
> https://github.com/whatwg/xhr/commits for an overview of the changes.
>

Received on Thursday, 3 October 2013 04:36:08 UTC