W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

Re: ISSUE-50: Should capturing EventListeners registered on the target fire?

From: Sergey Ilinsky <sergey@backbase.com>
Date: Thu, 23 Mar 2006 12:25:38 +0100
Message-ID: <015001c64e6c$82cc7630$8132a8c0@vientiane>
To: "Bjoern Hoehrmann" <derhoermi@gmx.net>
Cc: "\"Web APIs WG\"" <public-webapi@w3.org>

--- Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

> * Web APIs Issue Tracker wrote:
> >It is not entierly clear in DOM Level 2 Events if
> this is how things should be.
> Jonas discovered the relevant text, 1.2.2 has "A
> capturing EventListener
> will not be triggered by events dispatched directly
> to the EventTarget
> upon which it is registered." And Maciej found
> dispatchEvent09 in the
> DOM Level 2 Events test suite that tests for this.
> So the question is
> now whether we want to change this.
> -- 
> Björn Höhrmann · mailto:bjoern@hoehrmann.de ·
> http://bjoern.hoehrmann.de
> Weinh. Str. 22 · Telefon: +49(0)621/4309674 ·
> http://www.bjoernsworld.de
> 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 ·
> http://www.websitedev.de/ 


Why do you think the specifyed in DOM-Events module processing model 
should be changed? I think the existing behaviour where capture-type 
listeners are not being processed on the target fits the entire set 
of requirements that could be met. The model is clear enough, 
while being logical. 
In BackBase Presentation Client we have proper implementation of 
DOM-Event-Level-3 and we see how good it works.

Probably WEB-API group could develop a set of abstract test-cases to 
verify/prove the existing model?

Sergey Ilinsky/

System Architect
BackBase B.V.
Received on Thursday, 23 March 2006 11:25:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:20 UTC