[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 #146 from Hayato Ito <hayato@chromium.org> ---
(In reply to Olli Pettay from comment #143)
>  
> > 2. Events that are Always Stopped at...where?
> > The current spec of "Events that are Always Stopped" says "...stopped at the
> > root node of the node tree"
> > http://w3c.github.io/webcomponents/spec/shadow/#h-events-that-are-always-
> > stopped
> > 
> > Current our implementation allows older and younger shadow roots to receive
> > the event and stops before shadow hosts.
> hosts? plural?
> 
> mousemove _within_ older shadow dom shouldn't propagate to the younger
> shadow dom


That's orthogonal problem, which should be handled by event-related-target
algorithm and the following sentence in
http://w3c.github.io/webcomponents/spec/shadow/#event-dispatch

> If the relatedTarget and target are the same for a given node, its the event listeners must not be invoked. TouchEvent is not subject to this rule.


In addition to that, in this case, it's okay for the younger to see the mouse
move within the older for the same reason that the shadow tree can see mouse
move for distributed nodes in it's shadow host. I think the current algorithm
is designed to achieve that.

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

Received on Friday, 13 February 2015 03:08:51 UTC