[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 #70 from Jonas Sicking <jonas@sicking.cc> ---
I agree with comment 67 and comment 68. Order within a tree is much more
important than order between nodes in different trees.

And in comment 50 bz also suggests an event path where the total order of nodes
is arguably "non-sensical" since it jumps back and forth between two trees.

I'd even argue that the order of the non-insertion-point nodes makes a lot of
sense as it's currently defined by spec since it matches rendering order. This
means that if you click an icon inside a button inside a toolback that the
event goes first to the icon, then the button then the toolbar as it's bubbling
out. Even if the nodes are spread out over multiple shadow DOM trees.

I don't see a way to accomplish that if we also want to have a simple total
order between nodes?


That said, it's still not clear to me what the right answer is on the topic of
when/if to fire events on insertion points.

I do quite like the current feature that you can listen on an insertion point
to get notified about all the events that are inserted in that insertion point.
And it feels quite intuitive for authors that that is the case.

While you can generally wrap a <span> around the insertion point and add your
listeners there, that can affect rendering. For example if some of the nodes
involved in the rendering are rendered as tables/tablecells/tablerows.

It also will affect nested insertion points if the parent of the insertion
point that you are wrapping has a binding. Now it's the span that will get
distributed rather than all the nodes that were inserted in the insertion
point.

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

Received on Wednesday, 26 March 2014 22:34:06 UTC