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: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 20 Sep 2011 17:32:23 -0700
Message-ID: <CA+c2ei9jDkJ_WPPdeoSyt4M4d3k6jLnd-h292tVCidVR55078A@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Eric U <ericu@google.com>, arun@mozilla.com, Kyle Huey <me@kylehuey.com>, public-webapps@w3.org
On Tue, Sep 20, 2011 at 5:26 PM, Glenn Maynard <glenn@zewt.org> wrote:
> 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

Ooh, that's a good idea.

/ Jonas
Received on Wednesday, 21 September 2011 00:33:20 GMT

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