ISSUE-123: Rationale for feature strings
feature strings
Rationale for feature strings
- State:
- CLOSED
- Product:
- HISTORICAL: DOM3 Events [All Bugs and Issues use Bugzilla: http://tinyurl.com/Bugs-DOM3Events]
- Raised by:
- Doug Schepers
- Opened on:
- 2010-09-15
- Description:
- 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.)
]] - Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events] (from annevk@opera.com on 2011-08-15)
- Re: ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events] (from Jacob.Rossi@microsoft.com on 2011-08-12)
- ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events] (from sysbot+tracker@w3.org on 2010-09-15)
Related notes:
LAST CALL
Doug Schepers, 15 Sep 2010, 18:07:01The existance of an interface named "TextEvent" does not necessarily indicate the same thing as an implementation which claims support for DOM L3 Events TextEvents feature. While hasFeature isn't perfect (see other threads on this), an existing implementation exists. If other vendors implement extended feature strings accurately, then this will be the preferred method of feature detection.
Jacob Rossi, 15 Apr 2011, 04:40:17Display change log
