[Bug 21404] [Shadow]: 5.5 Event Dispatch references incorrect steps of event dispatching algorithm

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21404

--- Comment #10 from Hayato Ito <hayato@chromium.org> ---
(In reply to comment #9)
> (In reply to comment #8)
> > I guess that since element.addEventListener's third parameter, useCapture,
> > is 'false' in default, people is likely to have a mental model of 'event
> > listernes are called from inner to outer'.
> > That might support the idea of 'minicing bubbling events' for AT_TARGET
> > phase.
> 
> Right. Most of the time this parameter is false (very few use capture), so
> the order of events looks whacky: first listener is fired on the host that's
> farthest from the target.

Okay. Agreed. Let's change the order.
For the record, the new order should be:

For bubbling events:

  A          1 (C)  11 (B)
  B          2 (C)  10 (B)
  C (SH)             9 (T) 
  D          3 (C)   8 (B)
  E (SH)             7 (T)
  F          4 (C)   6 (B)
  G (Target)         5 (T)  


For non-bubbling events:

  A          1 (C)
  B          2 (C)
  C (SH)            7 (T) 
  D          3 (C)
  E (SH)            6 (T)
  F          4 (C)
  G (Target)        5 (T)  

Does this sound good?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 1 April 2013 03:44:39 UTC