[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 #170 from Koji Ishii <kojiishi@gmail.com> ---
(In reply to Olli Pettay from comment #169)
> (In reply to Koji Ishii from comment #167)
> > Hm, looks like we have some misunderstanding. Can you clarify what I miss?
> > 
> > 1. You'd like to change the algorithm in the current spec.
> yes

Great, thank you for your support.

> (http://jsbin.com/casoyi/edit?html,js,output
> Note, that uses the old syntax for <shadow>. It was agreed long ago <shadow>
> would need to have <content> as a child.
> But I can't now recall where that change was agreed. But that isn't really
> about this bug.)

I wasn't aware of that, will check.

> >Chrome Canary:
> >1. click on B1: B1, SIP1, SR1, H1, BODY, HTML, [object HTMLDocument], [object Window]
> >2. click on B2: B2, SR2, H2, BODY, HTML, [object HTMLDocument], [object Window]
> >3. selectstart on B3: B3, SR4, SIP2, SR5
> >4. selectstart on B4: B4, SIP2, SIP3, SR7, C3, SR6, H4, BODY, HTML, [object HTMLDocument], [object Window]
> 
> >Experimental impl on Chrome:
> >1. click on B1: B1
> Ok, so this case would need another tweak
> "Repeat while CURRENT is a shadow insertion point."
> ->
> "Repeat while CURRENT is a shadow insertion point and there is a shadow root
> distributed to it".
> 
> 2. click on B2: B2, SR2
> This is fixed by comment 163.

Ok, I'll try.

> 3. selectstart on B3: B3, SR4
> This is the expected behavior. selectstart shouldn't be exposed outside its
> initial shadow DOM.
> The spec says "The following events must always be stopped at the root node
> of the node tree" and SR4 is a root.
> 
> 4. selectstart on B4: B4
> and this is similar to (1)

True that text and algorithm contradict to each other here. Hayato confirmed
that the algorithm is correct. Please refer to bug 28008. IIUC, otherwise it
will contradict with the policy of creating younger shadow roots should not
change behavior of older shadow roots.

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

Received on Wednesday, 4 March 2015 00:08:18 UTC