W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2011

[whatwg] readystatechange for SCRIPT

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Sat, 10 Sep 2011 15:37:09 -0400
Message-ID: <4E6BBC65.2040202@mit.edu>
On 9/10/11 11:00 AM, Kyle Simpson wrote:
> So, can I clarify something? You have moved `onreadystatechange` and
> `readyState` off of the <script> element entirely, and onto the HTML
> element?

No.  They've been removed from elements (and windows) entirely.  They 
remain on Document.

> In regards to all the concern about double-firing of load detection
> logic, IE9 added both `onload` event firing to their existing script
> element's `onreadystatechange` firing.

In all modes?

> So, I'm not sure why we're rushing to fear these problems. A few years
> ago, maybe this was an issue, but I don't see how there's real evidence
> of current problems. Most script loaders are already immune to this
> problem.

Opera pointed to a specific script loader in the Facebook API that is 
not thus immune, as well as one in popcornjs.

Given an existence proof like that, "most" doesn't really cut it for me, 
unfortunately.

Or put another way, I would not be willing to implement readyState on 
scripts in in Gecko as things stand, without a lot stronger data 
supporting the fact that scripts no longer listen for both load and 
readystatechange.

-Boris
Received on Saturday, 10 September 2011 12:37:09 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:36 UTC