[Bug 21833] Under read* chaining during load event loadends should be suppressed

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21833

--- Comment #3 from Arun <arun@mozilla.com> ---
Solutions here might be:

1. Adding something like a synchronously updated LOADEND counter, maybe with
timestamp if absolutely necessary.  This is probably what at least two
implementations are doing, per listserv conversation, so the spec. could say
something like this.  It would be a "soft counter" not exposed to script, of
course.

2. Saying something explicitly in prose during "making progress events" and
error steps and abort steps about not firing a loadend if superseded by a new
read; e.g. something explicit about whether the read is initiated in onload,
onerror, or onabort.  But this is awkward, since it isn't advisable to have a
spec. need code analysis to determine when to fire loadend.

3. Make loadend itself fire synchronously, but this deviates from other event
models.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 30 May 2013 23:37:31 UTC