W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 13965] Exposing onreadystatechange on script elements seems to not be web-compatible unless they fire the event

From: <bugzilla@jessica.w3.org>
Date: Sun, 04 Sep 2011 14:26:10 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R0DeE-0005xX-7z@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13965

--- Comment #13 from Boris Zbarsky <bzbarsky@mit.edu> 2011-09-04 14:26:08 UTC ---
> but it fires `onreadystatechange` for "loaded" (or "complete") *before* it
> fires `onload`.

Interesting.  I tested precisely that in IE9, and I saw the onload firing
before the onreadystatechange...  Quite curious.

> IE fires "complete" instead of "loaded" when the script is purely pulled from
> cache.

That's insane.  Par for the course, I guess, but insane.  I don't see a need to
duplicate this behavior, honestly.  For one thing, a UA may have no idea
whether the script came from cache or not (think intermediate caches, for one
thing!).

I fail to see how scripts could possibly depend on whether another script "came
from cache" (whatever that even means, given intermediate caches).

I also fail to see why implementing something like what Opera did would not be
compatible with the web.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 4 September 2011 14:26:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:03 UTC