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

On Thu, 23 Mar 2006, Bjoern Hoehrmann wrote:
> 
> * 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:
> 
>  [...]
>   * XBL2 phase="capture|default" maps to useCapture

I don't see how XBL relies on any of the above, it'll just do what DOM 
Events says, regardless of what that is.

This question seems trivial to answer. Test the major browsers, do what 
the majority of them do. The IEs don't do capture, Mozilla does 2, Opera 
and Safari do 3. So we go with 3.

   http://hixie.ch/tests/adhoc/dom/events/capture/001.html

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Friday, 24 March 2006 19:22:55 UTC