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

On Fri, Oct 4, 2013 at 8:46 PM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Thu, Oct 3, 2013 at 6:35 AM, Takeshi Yoshino <tyoshino@google.com>
> wrote:
> > On Tue, Sep 3, 2013 at 9:00 PM, Anne van Kesteren <annevk@annevk.nl>
> wrote:
> >> 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)?
>
> No, if you look at
> http://xhr.spec.whatwg.org/#infrastructure-for-the-send%28%29-method
> "If the end user cancels the request" is about the end user, "If there
> is a network error" is about everything else.
>
>
> Sorry. I included network by mistake. I wanted to understand the abort
error well.

Q: cancel by abort() is abort error?
Q: any kind of network activity cancellation not due to network/timeout are
abort error?

Received on Friday, 4 October 2013 13:12:59 UTC