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


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
                 CC|                            |ian@hixie.ch
           Severity|normal                      |blocker

--- Comment #7 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-03 05:41:56 UTC ---
Would having <script> elements have a readyState IDL attribute that has the
following states, and for which an event gets queued whenever the value
changes, be ok?

 'uninitialized' - script file isn't loaded (or specified) yet, but UA is going
to preload it ASAP (after the "src" is set if it's not already set).

 'loaded' - script file is loaded, or, script file isn't loaded but UA isn't
going to preload it anyway so it doesn't matter.

 'complete' - script file is loaded and has executed. (I'll check with IE about
whether this change happens before or after onload, and whether the event gets
queued before or after onload.)

I believe this would allow both for the IE preload behaviour and for the
non-preload behaviour, and would be compatible with yandex and LABjs. (We want
to allow preload to be optional since it should, in theory, be just a
performance issue, and some UAs may prefer to err on the side of low bandwidth
usage rather than on the side of fast script execution.)

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 Saturday, 3 September 2011 05:41:58 UTC