W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 21 Sep 2011 17:34:54 -0700
Message-ID: <CA+c2ei_80jcTYG5P8GAkjPArfaEp2J21+n5BUaELMpeGG9S6NA@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Eric U <ericu@google.com>, arun@mozilla.com, Kyle Huey <me@kylehuey.com>, public-webapps@w3.org, Anne van Kesteren <annevk@opera.com>
On Wed, Sep 21, 2011 at 5:16 PM, Glenn Maynard <glenn@zewt.org> wrote:
> On Wed, Sep 21, 2011 at 7:51 PM, Eric U <ericu@google.com> wrote:
>> Again, that's not what the XHR2 spec says.  See my summary up-thread
>> about the actual behavior, and Anne can correct my interpretation if
>> I'm wrong.
> I don't know what you mean by "again"; this is the first time I've described
> this behavior.
> The spec says "The abort() algorithm can only be terminated by invoking
> open() from an event handler."  If you call open() from 5.6.2's onabort,
> then step 14 of the open() algorithm terminates abort(), and step 5.6.3
> never happens, thus onloadend is never fired and loadstart and loadend
> events are mismatched.

This sounds like a bug in the XHR spec as it doesn't fulfill the
invariants I listed.

/ Jonas
Received on Thursday, 22 September 2011 00:35:51 UTC

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