W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

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

From: Arun Ranganathan <arun@mozilla.com>
Date: Mon, 23 May 2011 18:19:13 -0700
Message-ID: <4DDB0791.5030909@mozilla.com>
To: arun@mozilla.com, Kyle Huey <me@kylehuey.com>
CC: Web Applications Working Group WG <public-webapps@w3.org>, Jonas Sicking <jonas@sicking.cc>, Eric Uhrhane <ericu@google.com>
On 5/23/11 6:14 PM, Arun Ranganathan wrote:
> On 5/23/11 1:20 PM, Kyle Huey wrote:
>> To close the loop a bit here, Firefox 6 will make the change to 
>> FileReader.abort()'s throwing behavior agreed upon here.  
>> (https://bugzilla.mozilla.org/show_bug.cgi?id=657964)
>>
>> We have not changed the timing of the events, which are still 
>> dispatched synchronously.
>
> The editor's draft presently does nothing when readyState is EMPTY, 
> but if readyState is DONE it is specified to set result to null and 
> fire events (but flush any pending tasks that are queued).
>
> http://dev.w3.org/2006/webapi/FileAPI/#dfn-abort
>
> Also note that we're NOT firing *both* error and abort; we should only 
> fire abort, and *not* error.
>
> I should change the spec. to throw.  Eric, you might change the spec. 
> (and Chrome) to NOT fire error and abort events :)

Sorry, to be a bit clearer: I'm talking about Eric changing 
http://dev.w3.org/2009/dap/file-system/file-writer.html#widl-FileSaver-abort-void 
to match http://dev.w3.org/2006/webapi/FileAPI/#dfn-abort

-- A*
Received on Tuesday, 24 May 2011 01:19:40 GMT

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