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: Glenn Maynard <glenn@zewt.org>
Date: Thu, 22 Sep 2011 11:48:33 -0400
Message-ID: <CABirCh8sgbnmbi_D1HMgzaAqsGBKMSGxnqwT+cMhTqBeCoQgvg@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: Eric U <ericu@google.com>, Jonas Sicking <jonas@sicking.cc>, arun@mozilla.com, Kyle Huey <me@kylehuey.com>, public-webapps@w3.org
On Thu, Sep 22, 2011 at 5:19 AM, Anne van Kesteren <annevk@opera.com> wrote:

>  I just tried this in FF6, and the behavior is inconsistent.  If the TCP
>> connection has been established, then it follows your interpretation, and
>> you get onloadstart, onabort, onloadstart, onloadend, onloadend [1][3].
>>  If the TCP connection hasn't yet been established [2][4], calling open()
>> from either onabort or onloadend throws NS_ERROR_IN_PROGRESS.
> But open() has to dispatch a readystatechange event. That will get
> somewhere in the middle of that, no?

Sorry, I meant calling send() throws NS_ERROR_IN_PROGRESS.

Glenn Maynard
Received on Thursday, 22 September 2011 15:49:02 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:35 UTC