-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added declarative shadow DOM #45
Conversation
</ul> | ||
</section> | ||
<section> | ||
<h3>Open Questions</h3> | ||
<ul> | ||
<li>---</li> | ||
<li>Mozilla would like to see more <a href="https://github.com/whatwg/dom/issues/831#issuecomment-988394185">real world uses cases</a> of Declarative Shadow DOM in the wild. Which is a bit of a catch-22 when it is only supported in one browser and requires a polyfill.</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There’s a bit of editorializing here, but sharing your bias on this one see no reason not to allow it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair, but I guess part of the premise of this proposal to help reduce JS (say for SSG) and or at least the overhead of it (SSR + hydration). I think it's probably why folks still stick with the light DOM rendering, or in my case for WCC, encourage the option for SSG.
But definitely recognize this is a group report, so we can definitely run it by the team at our next meeting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm!
SHA: c9572c6 Reason: push, by @Westbrook Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Adding Declarative Shadow DOM to the report.