On Mon, Mar 5, 2012 at 2:01 PM, Eric U er...@google.com wrote:
On Thu, Mar 1, 2012 at 11:20 AM, Arun Ranganathan
aranganat...@mozilla.com wrote:
Eric,
So we could:
1. Say not to fire a loadend if onloadend or onabort
Do you mean if onload, onerror, or onabort...?
No, actually. I'm
].
Of the list of 'hacks', we also implemented hack #2 to get the correct behavior.
-Original Message-
From: Eric U [mailto:er...@google.com]
Sent: Tuesday, March 06, 2012 12:16 PM
To: Arun Ranganathan
Cc: Web Applications Working Group WG
Subject: Re: FileReader abort, again
On Thu, Mar 1, 2012 at 11:20 AM, Arun Ranganathan
aranganat...@mozilla.com wrote:
Eric,
So we could:
1. Say not to fire a loadend if onloadend or onabort
Do you mean if onload, onerror, or onabort...?
No, actually. I'm looking for the right sequence of steps that results in
abort's
Eric,
So we could:
1. Say not to fire a loadend if onloadend or onabort
Do you mean if onload, onerror, or onabort...?
No, actually. I'm looking for the right sequence of steps that results in
abort's loadend not firing if terminated by another read*. Since abort will
fire an
Incidentally, the way XHR gets around this is to have open cancel any
in-progress abort. We could certainly do the same thing, having any
readAs* cancel abort().
On Tue, Feb 28, 2012 at 4:15 PM, Eric U er...@google.com wrote:
I like the Event Invariants writeup at the end. It's only
FileReader.abort is like a bad penny :)
However, I'm not sure it quite matches the normative text in one
respect. Where you say [8.5.6 step 4]: Terminate any steps while
processing a read method. Does that also terminate the steps
associated with an abort that terminated the read method?
On Wed, Feb 29, 2012 at 1:43 PM, Arun Ranganathan
aranganat...@mozilla.com wrote:
FileReader.abort is like a bad penny :)
However, I'm not sure it quite matches the normative text in one
respect. Where you say [8.5.6 step 4]: Terminate any steps while
processing a read method. Does that
On Wed, Feb 29, 2012 at 1:43 PM, Arun Ranganathan
Otherwise, if you start a new read in onabort [8.5.6 step 5],
you'll
still deliver the loadend [8.5.6 step 6].
This contradicts 8.5.9.2.1 Once a loadstart has been fired, a
corresponding loadend fires at completion of the read, EXCEPT if
On Wed, Feb 29, 2012 at 2:57 PM, Arun Ranganathan
aranganat...@mozilla.com wrote:
On Wed, Feb 29, 2012 at 1:43 PM, Arun Ranganathan
Otherwise, if you start a new read in onabort [8.5.6 step 5],
you'll
still deliver the loadend [8.5.6 step 6].
This contradicts 8.5.9.2.1 Once a loadstart
