[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 #30 from Olli Pettay <bugs@pettay.fi> ---
(In reply to Hayato Ito from comment #28)
> I think there is a confusion. 
I don't think so ;)


So let me explain the design principle of the
> current event path.
> 
> - An event can be dispatched across node trees.
> - If we view each node tree as a separate tree, there should be a *certain
> level* of consistency for the existing event dispatching model within the
> same node tree.
> 
> 
> For example, given a fig4
> (http://w3c.github.io/webcomponents/spec/shadow/index.html#distribution-
> results):
> 
> If child 1 is clicked, the event path would be:
>   [child1, IP1, IP3, IP3's parent, 2nd SR, 2nd SH, 1st SR, 1st SH, document]
> 
> For each node tree:
>  - For the document tree, the event path would be [child1, 1st SH, document]
>  - For 1st shadow tree, the event path would be [IP1, 2nd SH, 1st SR]
>  - For 2nd shadow tree, the event path would be [IP3, IP3's parent, 2nd SR]
The example just happens to make that look nice.
But if 1st shadow tree for example has a non-SH-node in the place of 2nd SH,
and
that node has 2nd SH as a child. Then for the 1st shadow tree the event path
would be [IP1, 2nd SH, the-parent-of-2nd-SH, 2ns SR]

Now, the-parent-of-2nd-SH is the parent of both IP1 and 2nd SH, and event goes
through both those siblings.

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

Received on Wednesday, 4 December 2013 06:40:47 UTC