[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 #141 from Koji Ishii <kojiishi@gmail.com> ---
With so much thanks to Olli, wchen, and Hayato, I've experimentally implemented
the proposed algorithm, and now I'm seeing two different results in our tests.

The two are minor, but since they are changes in the behavior not discussed in
this thread yet, any opinions/insights from anyone is also appreciated.

1. The proposed algorithm stops event path for orphaned nodes
When target nodes are not distributed, the event path in the current spec
bubbles up to Document, but the proposed algorithm stops. Example:

A
  SR
  B

Note that SR does not have IP. When an event fires on B, the event path is:
Current: B, SR, A, Document, Window
Proposed: B

This also occurs when younger shadow roots do not have any shadow insertion
points.

I think this is a subtle detail we can ignore, and this difference does not
prevent the proposed algorithm to be accepted. If anyone think differently,
appreciate comments.

2. Events that are Always Stopped at...where?
The current spec of "Events that are Always Stopped" says "...stopped at the
root node of the node tree"
http://w3c.github.io/webcomponents/spec/shadow/#h-events-that-are-always-stopped

Current our implementation allows older and younger shadow roots to receive the
event and stops before shadow hosts. The behavior was changed by the
experimental implementation, probably because the order was changed.

I can't determine if "the root node of the node tree" includes older/younger
shadow roots, I'll discuss with Hayato for clarification.

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

Received on Thursday, 12 February 2015 06:28:53 UTC