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:42:17 -0700
Message-ID: <BANLkTik+Fe_hQbH+uZu++hxmE8C2SqXhFw@mail.gmail.com>
To: Kyle Huey <me@kylehuey.com>
Cc: Web Applications Working Group WG <public-webapps@w3.org>, Jonas Sicking <jonas@sicking.cc>
It was likely just an oversight on my part that they differ.
It does seem a bit odd to dispatch error/abort/loadend if aborting
with no write in progress, so I favor the FileWriter/FileSaver
behavior, but as long as they match, I'm not too bothered.

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].
>
> - Kyle
>
Received on Tuesday, 17 May 2011 21:42:58 GMT

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