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: Eric U <ericu@google.com>
Date: Tue, 17 May 2011 14:43:52 -0700
Message-ID: <BANLkTi=A821KTp1fkhMCTAO-rRa27EB0GQ@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Kyle Huey <me@kylehuey.com>, Arun Ranganathan <arun@mozilla.com>, Web Applications Working Group WG <public-webapps@w3.org>
On Tue, May 17, 2011 at 2:41 PM, Jonas Sicking <jonas@sicking.cc> wrote:
> On Tue, May 17, 2011 at 2:35 PM, Kyle Huey <me@kylehuey.com> wrote:
>> The abort behaviors of FileReader and File[Saver|Writer] differ.  The
>> writing objects throw if the abort method is called when a write is not
>> currently under way, while the reading object does not throw.
>>
>> The behaviors should be consistent.  I don't particularly care either way,
>> but I believe Jonas would like to change FileReader to match
>> File[Saver|Writer].
>
> Yeah, since we made FileReader.readAsX throw when called in the wrong
> "state", I believe doing the same for abort() is the better option.
>
> / Jonas

Sounds good to me.
Received on Tuesday, 17 May 2011 21:44:31 GMT

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