W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2011

Re: Functions that Implement the EventListener Interface (DOM Level 3 Events)

From: Rob Brackett <rbrackett@apple.com>
Date: Tue, 14 Jun 2011 08:31:47 -0700
Cc: www-dom@w3.org
Message-id: <7259CCA9-31C1-4F6D-BF07-8603900A321B@apple.com>
To: Cameron McCormack <cam@mcc.id.au>
Ah, those links certainly make the intention much more clear. Thanks!

What is the process for suggesting a revision to the spec? At the very least, the wording for addEventListener's "listener" argument needs to be cleaned up so it doesn't read like it's not finished.

-Rob


On Jun 13, 2011, at 5:41 PM, Cameron McCormack wrote:

> Hi Rob.
> 
> Rob Brackett:
>> For what it's worth, I think WebKit's current behavior is preferable
>> (in my case, myConstructor.handleEvent() would have been called
>> instead of myConstructor()), though it is different from how Firefox,
>> Opera, and Chrome behave (myConstructor() would be called instead of
>> myConstructor.handleEvent()). At the very least, it would be nice the
>> get the wording here more clear.
> 
> Web IDL defines that for interfaces with [Callback] on them, such as
> EventListener [1][2], that the function itself takes precedence over the
> property [3].
> 
> [1] http://www.w3.org/TR/DOM-Level-3-Events/#webidl-events-EventListener
> [2] http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#eventlistener
> [3] http://dev.w3.org/2006/webapi/WebIDL/#native-objects
> 
> -- 
> Cameron McCormack ≝ http://mcc.id.au/
> 
Received on Tuesday, 14 June 2011 15:32:25 GMT

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