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:48:00 -0700
Message-ID: <BANLkTikaYMG3Yr6D46wWFHu2Gp4ogsjmcg@mail.gmail.com>
To: Eric U <ericu@google.com>
Cc: Kyle Huey <me@kylehuey.com>, Web Applications Working Group WG <public-webapps@w3.org>
On Tue, May 17, 2011 at 2:42 PM, Eric U <ericu@google.com> wrote:
> 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.

For what it's worth, FileReader.abort() currently follows what
XHR.abort() does, which is to do nothing if called in the "wrong"
state. I.e. no events are aborted and no exceptions are thrown.

/ Jonas
Received on Tuesday, 17 May 2011 21:48:57 GMT

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