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

Re: [FileAPI] Updates to FileAPI Editor's Draft

From: Arun Ranganathan <arun@mozilla.com>
Date: Tue, 21 Jun 2011 12:30:38 -0400
Message-ID: <4E00C72E.2070808@mozilla.com>
To: Jonas Sicking <jonas@sicking.cc>
CC: Jian Li <jianli@chromium.org>, Web Applications Working Group WG <public-webapps@w3.org>
On 6/7/11 5:04 PM, Jonas Sicking wrote:
> On Tue, Jun 7, 2011 at 11:51 AM, Jian Li<jianli@chromium.org>  wrote:
>> On Tue, Jun 7, 2011 at 11:23 AM, Jonas Sicking<jonas@sicking.cc>  wrote:
>>> On Tue, Jun 7, 2011 at 10:43 AM, Jian Li<jianli@chromium.org>  wrote:
>>>> I have a couple questions regarding abort behavior.
>>>> If the reading is completed and the loadend event has been fired, do we
>>>> want
>>>> to fire loadend event again when abort() method is called?
>>> No
>>>> Do we want to reset error to null or leave it intact when abort() method
>>>> is
>>>> called?
>>> If called after load/abort/error has fired the calling abort() should
>>> just throw an exception and not alter the FileReader object in any
>>> way.
>> Do you mean we should throw if abort() is called after load/abort/error has
>> been fired but before loadend event has been fired?
> Yes.
>> If so, what kind of exception should we throw?
> I need to get updated on the status on various exceptions, so I don't
> have an opinion on this at this time.
>> The spec only mentions that "If readyState = DONE set result to null."
> I actually disagree with that sentence.

So I'm not exactly sure we should throw here.  Why do you disagree?  
Have you revisited this opinion?  What should the behavior be?

-- A*

> / Jonas
Received on Tuesday, 21 June 2011 16:31:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:20 UTC