[whatwg] readystatechange for SCRIPT (Re: Feedback regarding script execution)
ian at hixie.ch
Thu Sep 8 14:15:48 PDT 2011
On Thu, 8 Sep 2011, Boris Zbarsky wrote:
> On 9/8/11 4:41 PM, Hallvord R. M. Steen wrote:
> > as far as I know Opera is currently the only browser that supports
> > both script.onload and script.onreadystatechange, and this is causing
> > us compatibility problems because many scripts set both and expect
> > only one of them to run. For this reason, we plan to drop
> > script.onreadystatechange support.
> That will break still other sites. That's why it's been added to the
> spec; it turned out that as long as script.onreadystatechange is not
> undefined (which the spec currently requires because it defines all on*
> attributes on all elements) there are sites that expect the event to be
> fired. Where by "sites" I mean at least Yandex maps so far in Gecko's
> experience of shipping this for a few weeks in nightlies.
> The other obvious option here is to move onreadystatechange from being
> on all elements to only being on some elements....
Yeah, that is rapidly becoming my conclusion too. A few exceptions like
this aren't going to kill us (per spec <marquee> already has a few
exceptions of its own), but I would like to keep it to a minimum if we at
all can. Having just one set of these event handlers that apply everywhere
simplifies the platform quite a bit.
I'd like to study some of the pages that break if they have both, though,
to see if there's anything simpler we can do first.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg