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: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 17 May 2011 14:41:34 -0700
Message-ID: <BANLkTinTiKxGL_3r45mckWsYX4u8tgVP9g@mail.gmail.com>
To: Kyle Huey <me@kylehuey.com>, Arun Ranganathan <arun@mozilla.com>
Cc: Web Applications Working Group WG <public-webapps@w3.org>, Eric Uhrhane <ericu@google.com>
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
Received on Tuesday, 17 May 2011 21:42:31 UTC

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