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

Hypothetical WebIDL block for EventTarget

From: Travis Leithead <travil@microsoft.com>
Date: Wed, 14 Oct 2009 19:26:43 +0000
To: "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <49142F02149340458FDD20841AD0AD5621F9F9C7@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
I realize I'm touching on a controversial topic, but I was wondering what feedback we might get by proposing that the EventTarget interface in DOM Level 3 Events be marked up with WebIDL as follows (I don't imagine controversy on any other interface):
 
[NoInterfaceObject]
interface EventTarget {
  void               addEventListener(in DOMString type, 
                                      in EventListener listener, 
                                      in boolean useCapture);
  void               removeEventListener(in DOMString type, 
                                         in EventListener listener, 
                                         in boolean useCapture);
  // Modified in DOM Level 3:
  boolean            dispatchEvent(in Event evt)
                                   raises(EventException, 
                                   DOMException);
};

Note, this is different from http://dev.w3.org/2006/webapi/WebIDL/dom/dom2events.idl
The point of contention is whether EventTarget should be bound to an "interface object" in the ECMAScript binding or whether it participates in the mix-in algorithm, however that will end up working (not finalized in WebIDL at the moment).

For reference:

Browser     this.hasOwnProperty("EventTarget")
===============================================
IE8		false
FF3.5		false (but EventTarget.prototype exists)?
Safari4	false
Opera10	false
Received on Wednesday, 14 October 2009 19:27:20 GMT

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