[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 #99 from Hayato Ito <hayato@chromium.org> ---
The following has been on my radar for a long time:

- Whether calling event.stopPropagation() should affect the event dispatching
in other node trees or not.


AFAIR, I think this is the first time when this topic is being discussed in the
Shadow DOM spec bugzilla.

In the current spec, calling event.stopPropagation() in a node tree affects the
event dispatching in other node trees, as you notice.

In the past, I thought that we shouldn't make event.stopPropagation() affect
the behavior of event dispatching in node trees other than the current node
tree. I thought that an event dispatching in each node tree must be completely
*independent*. However, no one has taken care of this topic so far, except for
me.

This is the typical situation where it's difficult to satisfy both worlds - the
tree of trees world and the composed tree world.

I prefer the current rule. Calling an event.stopPropagation stops an entire
event dispatching, including event dispatching in other node trees. It's simple
and easy to implement and might be useful for some situations.

However it's worth discussing. I think we haven't have enough opinions from web
developers about this topic.

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

Received on Monday, 31 March 2014 08:02:49 UTC