W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events]

From: Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 15 Sep 2010 17:49:51 +0000
To: public-webapps@w3.org
Message-Id: <E1Ovw7D-0000eq-6K@nelson.w3.org>

ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events]

http://www.w3.org/2008/webapps/track/issues/123

Raised by: Doug Schepers
On product: DOM3 Events

Simon Pieters <http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html>:
[[
What's the use case for extended feature strings for event types
(hasFeature('Events.click', ''))? Opera, WebKit and Gecko don't support
this. [1]

What's the use case for feature strings for event interfaces
(hasFeature('KeyboardEvent', '') or hasFeature('Events.KeyboardEvent'))?
The spec says it's for backwards compatibility, but Opera, WebKit and
Gecko don't support this. [2] It's easier to test for event interfaces by
checking if the interface object exists as a property on the global
object, i.e. window.KeyboardEvent. (Opera currently doesn't expose
KeyboardEvent on window, but that's something we should fix.)

]]
Received on Wednesday, 15 September 2010 17:49:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT