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

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

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Thu, 23 Mar 2006 04:05:22 +0100
To: Web APIs WG <public-webapi@w3.org>
Message-ID: <603422p827gusul8skoc6o0dj73llsi4jl@hive.bjoern.hoehrmann.de>

* Web APIs Issue Tracker wrote:
>In any event, this needs to be clarified in DOM Level 3 Events.

Thinking about this, I see three options:

  1) the capture phase is accomplished at the target and all its
     ancestors, useCapture == true registers listener for the
     capture phase

  2) the capture phase is accomplished only at the target's
     ancestors, useCapture == true registers listener for the
     target and capture phase

  3) the capture phase is accomplished only at the target's
     ancestors, useCapture == true registers listener for the
     capture phase only

I think we should do 3) which has the following benefits:

  * DOM Level 3 Events unambiguously specified that for >3 years
  * ... so the editor does not need to change the draft in any way
  * most implementations I am aware of implement it
  * XML Events ev:phase="capture|default" maps to useCapture
  * XBL2 phase="capture|default" maps to useCapture
  * I wrote code that depends on it

I have some sympathy for 2) (what Mozilla does) but I don't
see strong enough reasons that outweight the benefits above.
-- 
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/ 
Received on Thursday, 23 March 2006 03:05:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT