- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Fri, 17 Jun 2011 20:01:31 +0300
- To: Anne van Kesteren <annevk@opera.com>
- CC: David Flanagan <dflanagan@mozilla.com>, Ms2ger <ms2ger@gmail.com>, www-dom@w3.org
On 06/17/2011 07:09 PM, Anne van Kesteren wrote:
> On Wed, 15 Jun 2011 13:01:48 +0200, Ms2ger <ms2ger@gmail.com> wrote:
>> On 06/15/2011 07:14 AM, David Flanagan wrote:
>>> EventListener is declared to be a [Callback], but unlike the [Callback]
>>> types in HTML, it does not have the [NoInterfaceObject] attribute. This
>>> seems to mean that implementations must create a useless EventListener
>>> property in the global namespace. And by my reading of WebIDL, we're
>>> also supposed to have EventListener.prototype.handleEvent, even though
>>> no host object will ever be created that inherits that method.
>>>
>>> Firefox 4 defines an EventListener object, but it has no prototype
>>> property and doesn't seem to be good for anything.
>>>
>>> Current versions of Chrome and Safari simply do not define
>>> EventListener. I think this is the way to go.
>>
>> Done.
>>
>> http://dvcs.w3.org/hg/domcore/rev/a48d3dccf595
>
> Can we also make it FunctionOnly in ECMAScript?
>
>
No. { handleEvent: function() {} }
is commonly used.
In general, I see no reason for FunctionOnly.
Though, browsers seem to implement onfoo listeners as
FunctionOnly.
Olli
Received on Friday, 17 June 2011 17:02:43 UTC