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

Creating a new element for the sole purpose of creating a shadow tree greatly concerns me.

For example, if we're defining a custom element, you wouldn't want to have another element outside a shadow tree of that custom element so using `shadowroot` element inside `template` element doesn't make sense. One approach to solve that discrepancy is to use `shadowroot` element itself to define a custom element. However, it would mean that depending on whether you'd like to use a shadow root or not, you have to use `template` or `shadowroot`, and the browser engine have to support the set of attributes and semantics in both elements.

Alternatively, we can define some exotic behaviors like all other nodes but `shadowroot` is ignored when defining a custom element. But this would create new behavior difference between when `shadowroot` is used standalone and when it's used to define a custom element.

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