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

Re: setCurrentTarget and duplicate event listeners (Was: DOM Level 3 Event's some weird stuff....)

From: Christian Parpart <cparpart@surakware.net>
Date: Wed, 2 Oct 2002 17:44:04 +0200
To: www-dom@w3.org
Cc: Philippe Le Hegaret <plh@w3.org>
Message-Id: <200210021744.08707.cparpart@surakware.net>

Hash: SHA1

On Wednesday 02 October 2002 2:31 pm, Philippe Le Hegaret inspired the 
electrons to say:
> On Wed, 2002-10-02 at 04:12, Christian Parpart wrote:
> > I'd prever an setCurrentTarget function getting a parameter of type
> > "EventTarget".
> It is indeed a clear mistake in the CustomEvent interface. Even if it is
> expected that every node would implement the EventTarget interface, this
> module could be reuse outside the context of a DOM tree (with the DOM
> CSS for example).

So, who will fix this mistake? And, when will it be fixed? Where are the ppl 
talking direktly about the modifications to such specs?

> > Furthermore:
> >
> > The EventTarget's function addEventListener.addEventListenerXX does only
> > put the new listener into the list if it is unique, other wise the
> > duplicate is discarded. What duplicate? The old one or the new one?
> Given that they are duplicate, i.e. the same event listener, does this
> really matter?

Yes, but it has been answered by you below, thanks ;)

> > And, what's equality
> > in the EventListener's object? Must the EventListener be of the same
> > interface? or even the same instance (object)?
> The same event listener, i.e. the same function reference is the case of
> ECMAScript or the same object instance in Java.

Exactly that's been my problem, thanks, it's fixed by now ;)

Version: GnuPG v1.0.7 (GNU/Linux)

Received on Wednesday, 2 October 2002 11:44:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:10 UTC