- From: <bugzilla@jessica.w3.org>
- Date: Fri, 26 Apr 2013 18:09:02 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21833
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |travil@microsoft.com
--- Comment #1 from Travis Leithead [MSFT] <travil@microsoft.com> ---
One rationale for this, is that when the chained read is started in the load
event, if the loadend event then fires, naïve JavaScript code won't distinguish
the loadend event from the previous read from the loadend event of the current
read.
We think it's better to not fire loadend in the chaining case, so that
JavaScript code won't need to add special case code to ignore the loadend event
for the previous read.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 26 April 2013 18:09:04 UTC