W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 22 Sep 2011 11:10:53 +0200
To: "Eric U" <ericu@google.com>, "Glenn Maynard" <glenn@zewt.org>
Cc: "Jonas Sicking" <jonas@sicking.cc>, arun@mozilla.com, "Kyle Huey" <me@kylehuey.com>, public-webapps@w3.org
Message-ID: <op.v17c4fe164w2qv@annevk-macbookpro.local>
On Wed, 21 Sep 2011 20:12:17 +0200, Glenn Maynard <glenn@zewt.org> wrote:
> Yuck.  I agree that's not a good thing to mimic for the sake of
> consistency.  Anne, is this intentional, or just something XHR is just  
> stuck with for compatibility?  It looks like a new problem in XHR2--this  
> couldn't happen in XHR1, because there was no abort event fired before  
> loadend.

The send() method can be terminated in similar fashion.

I made this change almost a year ago now. It was to prevent weird  
situations from occurring event-wise if you invoke open() from one of the  
events dispatched by e.g. send() or abort(). One of the silly things from  
XMLHttpRequest is that open() can always be invoked. This seemed like the  
simplest way of dealing with that.

I am open to suggestions however (and tests!).

Anne van Kesteren
Received on Thursday, 22 September 2011 09:11:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:35 UTC