[Bug 22344] [Shadow]: projecting into <shadow>

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

Jan Miksovsky <jan@quickui.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan@quickui.org

--- Comment #3 from Jan Miksovsky <jan@quickui.org> ---
I'm also of the opinion that this would be a huge win. I've built a number of
component-oriented web apps using a framework that effectively supports the
feature proposed here. In the process of porting components from that framework
to custom elements with shadow DOM, I've been running into some significant
challenges. See
http://blog.quickui.org/2013/06/11/puzzle-define-html-custom-element-subclasses-that-can-fill-in-base-class-insertion-points/
for a discussion of those issues; also see data in the first comment of that
post which suggest this feature would receive significant use in custom element
collections.

I believe this proposal is a natural extension to the Shadow DOM conceptual
model. I, and at least one other early Polymer user, independently expected
<shadow> to work this way — and were disappointed when it did not. This is a
statistically insignificant set of data points, but nevertheless, the fact that
early Shadow DOM users anticipate that this will work suggests it would be a
very natural extension of the spec'ed behavior.

One note: I would propose that, if <shadow>stuff</shadow> appears in a shadow
subtree with no older subtree (that is, there is no older shadow to fill in),
then "stuff" should get rendered as default content. This is the current
behavior in which <shadow> renders default content when no older subtree
exists.

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

Received on Thursday, 13 June 2013 22:33:07 UTC