[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 #148 from Koji Ishii <kojiishi@gmail.com> ---
(In reply to Olli Pettay from comment #143)
> (In reply to Koji Ishii from comment #141)
> > 
> > 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
> 
> But shouldn't B's destination insertion points be empty and from B event
> propagate to A.
> Or do I misunderstand your example?
> (B is a child node of A)

Sorry, I simplified the test case too much. The reproducible case is:

A
  SR
    SIP
  B

In this tree, B's destination insertion point is not empty, but B is not
distributed. When an event fired on B:
Current: B, SIP, SR, A, Document, Window
Proposed: B

So the two cases are similar but hit different causes:
1.1. When the shadow tree contains <shadow> but no <content>
1.2. When the younger shadow tree does not contain <shadow>

When the shadow tree does not contain either <shadow> nor <content>, you're
right that both algorithms produce the same results.

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

Received on Friday, 13 February 2015 04:45:31 UTC