[Bug 23887] [Shadow] Put only the final destination insertion point to the event path

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

--- Comment #72 from Olli Pettay <bugs@pettay.fi> ---
(In reply to Dimitri Glazkov from comment #71)

> Cons:
> - increased complexity
Slower event dispatch since event target chain creation becomes
more complicated because ... see the next point

> - (please add more)
Inconsistent targeting from target T to T' in the event target chain,
which makes event dispatch less intuitive when one needs to think about the
whole event dispatch, not only local shadow tree.
And because of .stop*Propagation() for example one needs to think about the
whole
path in some cases, not only local parts. Same with default handling. If you
use <a> in the
shadow trees and click somewhere, which link to follow?  The first shadow tree
can affect to the behavior of the nested shadow trees. 


> 
> Pros:
> - more intuitive for the consumer localized to any given tree
> - useful to listen for events coming out of elements, distributed to
> insertion points
> - fallback content is handled consistently


(I'm not saying pros aren't pros)





I guess XBL1 doesn't have this problem since it doesn't have explicit insertion
points,
so event propagation follows always the natural path.

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

Received on Thursday, 27 March 2014 17:19:31 UTC