- From: Eric U <ericu@google.com>
- Date: Tue, 17 May 2011 14:51:54 -0700
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: Kyle Huey <me@kylehuey.com>, Web Applications Working Group WG <public-webapps@w3.org>
On Tue, May 17, 2011 at 2:48 PM, Jonas Sicking <jonas@sicking.cc> wrote: > 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. Ah, my mistake; I was reading http://www.w3.org/TR/FileAPI/#abort instead of http://dev.w3.org/2006/webapi/FileAPI/#abort.
Received on Tuesday, 17 May 2011 21:52:33 UTC