[Bug 22344] [Shadow]: Distribute into <shadow>, project into older shadow root

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22344

--- Comment #37 from Scott Miles <sjmiles@chromium.org> ---
Your A, B, and C are true for anything that re-projects. IOW, if you replace
<shadow> with <x-foo> you have all the same scenarios and there is no magic
escape hatch. Similarly, if you remove re-projection from the example and use
only content nodes, position is still semantically relevant and one must be
conscious of it.

>From that standpoint, I don't see why <shadow> should have different behavior.

If we were to solve that problem more generally, that would make more sense to
me. E.g. if we introduce a special selector to mean "leftovers".  We have users
asking for this already.

I realize that our request for an 'implicit content' in <shadow> is also
exceptional, and I'm arguing against exceptions, but that exception is only for
syntactic sugaring and is not a new semantic.

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

Received on Thursday, 7 November 2013 04:43:08 UTC