Skip to content
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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Aug 25, 2022
Merged

added declarative shadow DOM #45

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f32b764
added declarative shadow DOM
thescientist13 Aug 21, 2022
b5fe274
Merge branch 'main' into report-2022-add-declarative-shadow-dom
Westbrook Aug 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 29 additions & 11 deletions reports/2022.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,10 @@
name: "Alan Dávalos",
url: "https://github.com/alangdm",
},
{
name: "Owen Buckley",
url: "https://github.com/thescientist13",
},
{
name: "Caleb Williams",
url: "https://github.com/calebdwilliams"
Expand Down Expand Up @@ -592,57 +596,71 @@ <h3>Links</h3>
<dt>Previous WCCG Report(s)</dt>
<dd><a href="https://w3c.github.io/webcomponents-cg/index.html#declarative-shadow-dom">2021</a></dd>
<dt>GitHub issues:</dt>
<dd>---</dd>
<dd><a href="https://github.com/whatwg/dom/issues/831">https://github.com/whatwg/dom/issues/831</a></dd>
<dt>Browser positions:</dt>
<dd>---</dd>
<dd><a href="https://chromestatus.com/feature/5191745052606464">Chrome (Shipped)</a></dd>
<dd><a href="https://github.com/mozilla/standards-positions/issues/335">Mozilla</a></dd>
<dd><a href="https://github.com/WebKit/standards-positions/issues/12">Safari</a></dd>
</dl>
</section>
<section>
<h3>Description</h3>
<p>---</p>
<p>Declarative Shadow DOM is a mechanism to express Shadow DOM using only HTML, with no dependency on JavaScript, much like light DOM can be declaratively expressed today.</p>
</section>
<section>
<h3>Links</h3>
<ul>
<li>---</li>
<li><a href="https://web.dev/declarative-shadow-dom">Declarative Shadow DOM</a></li>
</ul>
</section>
<section>
<h3>Status</h3>
<ul>
<li>---</li>
<li>Partial consensus, some implementation</li>
</ul>
</section>
<section>
<h3>Initial API Summary/Quick API Proposal</h3>
<p>Summary or proposal based on current status; paragraph(s) and code.</p>
<p>
<pre>
&lt;host-element&gt;
&lt;template shadowroot="open"&gt;
&lt;slot&gt;&lt;/slot&gt;
&lt;/template&gt;
&lt;h2>Light content&lt;/h2>&gt;
&lt;/host-element>
</pre>
</p>
</section>
<section>
<h3>Key Scenarios</h3>
<p>---</p>
<p>Server-Side Rendering: Without Declarative Shadow DOM, servers cannot deliver complete websites that include web component content. Markup cannot be efficiently delivered and then hydrated with JavaScript client-side.</p>
<p>JavaScript-less environments: Many web components could be implemented without JavaScript, taking advantage of encapsulated DOM and styles. However, web components cannot currently be rendered by users who have JavaScript disabled. Developers who are more comfortable with markup than with scripting may avoid shadow DOM altogether due to its tight coupling with JavaScript..</p>
</section>
<section>
<h3>Concerns</h3>
<ul>
<li>---</li>
<li>Mozilla considers this to be non-harmful, though debates the merits on ROI to developers weighed against the added complexity to be added to the HTML parser from a performance perspective.</li>
<li>Safari would like to see compatibility with Scoped Element Registry addressed first.</li>
</ul>
</section>
<section>
<h3>Dissenting Opinion</h3>
<ul>
<li>---</li>
<li>N / A</li>
</ul>
</section>
<section>
<h3>Related Specs</h3>
<ul>
<li>---</li>
<li><a href="https://github.com/WICG/webcomponents/issues/716">Scoped Element Registries</a></li>
</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>
Copy link
Collaborator

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.

Copy link
Collaborator Author

@thescientist13 thescientist13 Aug 21, 2022 •
edited
Loading

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.

<li>Safari would like to <a href="https://github.com/whatwg/dom/issues/831#issuecomment-797845645">get consensus on the solution for Scoped Element Registries first.</a></li>
</ul>
</section>
</section>
Expand Down