28008 2015-02-13 01:32:40 +0000 [Shadow] Should "Events that are Always Stopped" include destination insertion points? 2015-04-07 08:07:53 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified All All RESOLVED FIXED P2 normal --- 23887 1 kojiishi hayato annevk bzbarsky dglazkov hayato jonas mike public-webapps sorvell sorvell wchen public-webapps-bugzilla oldest_to_newest 117878 0 kojiishi 2015-02-13 01:32:40 +0000 5.1 Events that are Always Stopped[1] states that: > The following events must always be stopped at the root node of the node tree While by following the algorithm in the event path calculation algorithm in 5.2 Event Paths[2], it includes "the destination insertion points of CURRENT". Either the wording of 5.1 or the algorithm need to change. [1] http://w3c.github.io/webcomponents/spec/shadow/#events-that-are-always-stopped [2] http://w3c.github.io/webcomponents/spec/shadow/#dfn-event-path-calculation-algorithm 117883 1 hayato 2015-02-13 04:43:01 +0000 The algorithm is correct and intentional: We should fix the wording like this: > The following events must always be stopped at the root node of *youngest shadow tree*. 117886 2 annevk 2015-02-13 08:05:57 +0000 Please see bug 20247 comment 10. 117887 3 hayato 2015-02-13 08:15:23 +0000 (In reply to Anne from comment #2) > Please see bug 20247 comment 10. Thanks, but I'm afraid bug 20247 is an orthogonal issue. Even when we can resolve bug 20247, this issue, *where* we should stop an event, still apply. I'm totally supportive for bug 20247 comment 10, but I've not started on working bug 20247 yet... 118244 4 hayato 2015-03-03 07:59:59 +0000 Fixed at https://github.com/w3c/webcomponents/commit/2a3b7ed34bdbfb8ab095c914d41bf22703a117f5 119302 5 hayato 2015-04-07 08:07:53 +0000 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.