W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 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: Mon, 29 Aug 2011 21:42:19 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qy9b1-0000F6-NA@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13965

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzbarsky@mit.edu

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> 2011-08-29 21:42:19 UTC ---
See https://bugzilla.mozilla.org/show_bug.cgi?id=682554#c4 for some background.

In short, yandex is using |element.onreadystatechange == null| to detect
support for firing readystatechange events on <script> elements.  Presto and
Trident fire those events.  WebKit and Gecko do not, and used to have
.onreadystatechange test undefined on script elements, until Gecko tried
implementing this part of the spec.

The options here in terms of web compat are to either only have on* properties
exist on elements they make sense on (which I would somewhat prefer, since it
would simplify capability detection of the sort yandex was trying for) or to
spec and implement readyState and readystatechange events on <script> elements.
 Or both, since I doubt Presto and Trident will be removing their
readyState-on-script stuff, and since I do think that only exposing events on
the elements they make sense for improves the capability-detection situation.

-- 
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 Monday, 29 August 2011 21:42:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:17 UTC