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

So I think it depends on how instantiating the shadow root works. For example, if we're going with the route that `shadowroot` is some sort of macro syntax in parser which hoists its children into shadow root, and the element itself disappears, it probably doesn't make much sense to use `template` element for this because the semantics is so different.

On the other hand, if the semantics of this feature is that `shadowroot` simply defines the template from which the actual shadow root is generated, then using `template` makes a lot more sense. For example, imagine that we added the support for https://github.com/whatwg/html/issues/2254, then you should imagine we also want to support stamping out parts of the shadow tree using some values in a JS object or from content attributes of the shadow host.

There is a lot of open questions, and the best way to answer these would be have a list of concrete use cases for which this feature would be used.

So could you please list a very concrete use case (e.g. with an actual HTML & CSS for a concrete component, not just hypothetical generic problem) for which this feature is trying to address / useful?

-- 
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-333417803