[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 #33 from Hayato Ito <hayato@chromium.org> ---
(In reply to Olli Pettay from comment #32)
> (In reply to Olli Pettay from comment #22)
> 
> > > that node has 2nd SH as a child. Then for the 1st shadow tree the event path
> > 
> > In this case, IP3 cannot select nodes which are distributed into IP1.
> > Because IP1 is not a child node of 2nd SH.
> > That means CHILD1's destination insertion point is [IP1], rather than [IP1,
> > IP3].
> 
> Hmm, was my example wrong. Trying to find a better example.

Yeah, it might be better to have a better example.
Especially, I am curious whether we can create an example which hits the
following case A):

> A). In some shadow trees, an insertion point receives an event, but its parentNode doesn't receive an event. That's odd!

If we can create an example which causes A), I think it might be worth to fix
the current spec.


> 
> 
> 
> Anyhow, there is still no example where non-final-destination insertion
> points are needed in the event path and since this makes event propagation
> inconsistent with the rest to the platform, there is no need to make this
> special case.

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

Received on Tuesday, 10 December 2013 13:25:19 UTC