Re: [whatwg/dom] Declarative Shadow DOM (#510)

> I'm not seeing how they help at all with the problem of injecting the contents of an element into its parent's shadow root.

Using a template to define a custom element should certainly put the instantiated template into a shadow tree. So it's extremely relevant here. We definitely don't want to have two completely different mechanisms to define the contents of a shadow tree.

> The interesting part of this problem is that you've written some HTML that you want to use as some particular element's shadow root, rather than as the shadow root of all elements with the same name, so the 2013 proposal isn't helpful. The HTML doesn't need data-binding, since it's written out literally, so the January proposal isn't helpful.

What's relevant here is that both defines the contents of a shadow root.

In general, we shouldn't have two completely different mechanisms to define the contents of a shadow tree for this use case and declarative custom elements. That's confusing for authors, and makes the Web platform as a whole less coherent & confusing.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/510#issuecomment-332042712