Re: [FileAPI] FileReader.abort() and File[Saver|Writer].abort have different behaviors

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 UTC