W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2010

Re: Partial review of DOM 3 Events

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Wed, 06 Oct 2010 21:12:10 +0300
Message-ID: <4CACBBFA.2070904@helsinki.fi>
To: Simon Pieters <simonp@opera.com>
CC: "www-dom@w3.org" <www-dom@w3.org>
On 10/06/2010 09:02 PM, Simon Pieters wrote:
> On Wed, 06 Oct 2010 19:57:40 +0200, Olli Pettay
> <Olli.Pettay@helsinki.fi> wrote:
>
>> On 09/10/2010 12:58 PM, Simon Pieters wrote:
>>> Here's a partial review of DOM 3 Events
>>> http://www.w3.org/TR/2010/WD-DOM-Level-3-Events-20100907/
>>>
>>>
>>> What's the use case for extended feature strings for event types
>>> (hasFeature('Events.click', ''))? Opera, WebKit and Gecko don't support
>>> this. [1]
>>
>> Use case is to detect whether the browser claims to dispatch such
>> (trusted) events.
>
> Why would you want to detect that? How can you be sure that what the
> browser claims is true?

Well, onfoo detection might be true too, even though
browser doesn't ever fire the event, or support it in
any way.


>
>> Currently
>> if (element.onfoo) { ... }
>> is occasionally used for detecting support for some events, but that
>> doesn't really work since not all events have onfoo event listeners.
>
> Have you considered adding onfoo listeners for all events?
>
>> (And note, DOM 3 Events isn't just trying to document what is currently
>> supported.)
>
Received on Wednesday, 6 October 2010 18:12:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:06 GMT