- From: <bugzilla@jessica.w3.org>
- Date: Wed, 04 Dec 2013 04:14:26 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23887 --- Comment #28 from Hayato Ito <hayato@chromium.org> --- I think there is a confusion. 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] -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 4 December 2013 04:14:36 UTC