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: Glenn Maynard <glenn@zewt.org>
Date: Tue, 20 Sep 2011 20:26:13 -0400
Message-ID: <CABirCh8YUmN68qy2enRkxXfO7d_Nq3esgSGO8_HreCvafhHWOw@mail.gmail.com>
To: Eric U <ericu@google.com>
Cc: Jonas Sicking <jonas@sicking.cc>, arun@mozilla.com, Kyle Huey <me@kylehuey.com>, public-webapps@w3.org
On Tue, Sep 20, 2011 at 8:01 PM, Eric U <ericu@google.com> wrote:

> I have a read running, and at some point I abort it--it could be in
> onprogress or elsewhere.  In onabort I start another read.  In
> onloadstart I abort again.  Repeat as many times as you like, then let
> a read complete.  I believe we've specced that the event sequence
> should look like this:
>
> loadstart
> [progress]*
> ------[events from here to XXX happen synchronously, with no queueing]
> abort
> loadstart
>
abort
> loadstart
>

XHR handles this by not allowing a new request to be opened until the
abort() method terminates.  Could that be done here?  It seems like an
important thing to be consistent about.

http://dev.w3.org/2006/webapi/XMLHttpRequest/#the-abort-method

-- 
Glenn Maynard
Received on Wednesday, 21 September 2011 00:26:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT