- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Apr 2015 08:07:53 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28008 --- Comment #5 from Hayato Ito <hayato@chromium.org> --- Let me add a note in more reader friendly way here: (1) "Events that are always stopped" are stopped at the boundary between the *youngest* shadow root and it's shadow host. (2) "Events that are always stopped" are *NOT* stopped at the boundary between the older shadow root and the shadow insertion points in the younger shadow root. This situation, (2), is very similar to the following situation: (3) "Events that are always stopped" are *NOT* stopped at the boundary between the child node, A, of the shadow host and A's destination insertion point. In other words, the sub-path, from the youngest shadow root to it's shadow host, is the only moment where an event is propagating from "Child Component" to "Parent Component". (2) and (3) are not. I might add this note to the spec itself as a non-normative note. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 7 April 2015 08:07:57 UTC