- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Fri, 17 Jun 2011 13:04:58 -0400
- To: www-dom@w3.org
On 6/17/11 12: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? That is, make this not work? node.addEventListener({ handleEvent: function() { /* something */ } }, "eventname", false); I'm pretty sure this pattern is used on the web. -Boris
Received on Friday, 17 June 2011 17:05:26 UTC