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

```html
<div>
  <template shadowrootmode=closed>
    <my-fancy-wrapper>
      Some fancy wrapper that decorates the slotted content.
      This custom element also has access to the shadow root.
      <slot></slot>
    </my-fancy-wrapper>
  </template>
  Some light DOM content that script can see and manipulate
</div>
```

I'm sure there are many creative examples. 

> Since `<div>` with closed DSD works great, and is useful, I can't see why anyone would want to remove the feature. For "parity"? Who benefits from removing this feature?

@annevk I think this last question is the best one - how do **developers** benefit from arbitrarily restricting this functionality? And how do they benefit from having a lack of parity between imperative and declarative shadow dom? It means you can build things with Javascript that you can't use with server side rendering, at a minimum.

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

Message ID: <whatwg/dom/issues/831/1693549512@github.com>