Skip to content

Add scoped custom element registries #51

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

Merged
merged 1 commit into from
Sep 1, 2022
Merged

Add scoped custom element registries #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
38 changes: 30 additions & 8 deletions reports/2022.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -544,19 +544,33 @@ <h3>Links</h3>
<dt>Previous WCCG Report(s)</dt>
<dd><a href="https://w3c.github.io/webcomponents-cg/index.html#scoped-element-registries">2021</a></dd>
<dt>GitHub issues:</dt>
<dd>---</dd>
<dd><a href="https://github.com/WICG/webcomponents/issues/716">WICG/webcomponents#716</a></dd>
<dt>Browser positions:</dt>
<dd>---</dd>
<dd>
<ul>
<li>
<a href="https://github.com/WebKit/standards-positions/issues/38">WebKit</a>
</li>
<li>
<a href="https://groups.google.com/a/chromium.org/g/blink-dev/c/um-9YjJWyEQ/m/MhKN0L7FAgAJ">Chromium</a>
</li>
<li>
<a href="https://github.com/mozilla/standards-positions/issues/424">Mozilla</a>
</li>
</ul>
</dd>
</dl>
</section>
<section>
<h3>Description</h3>
<p>---</p>
<p>Scoped element registries allow custom element definitions to be scoped to one or more shadow roots. This allows the same tag name to be used with different implementations in different parts of the page, greatly reducing tag name collisions.</p>
</section>
<section>
<h3>Status</h3>
<ul>
<li>---</li>
<li>Chromium: prototyping</li>
<li>WebKit: ?</li>
<li>Mozilla: ?</li>
</ul>
</section>
<section>
Expand All @@ -565,18 +579,24 @@ <h3>Initial API Summary/Quick API Proposal</h3>
</section>
<section>
<h3>Key Scenarios</h3>
<p>---</p>
<ul>
<li>Building an app npm lbiraries that define elements. npm may duplicate packages and therefore custom element definitions.</li>
<li>Complex multi-team applications. Sub-teams often develop and deploy subsystems separately and may include multiple copies of libraries that define custom elements.</li>
<li>Complex elements with other custom elements as internal implementation detail. These elements may not want to take up names in the global registry for their sub-components.</li>
<li>Distributing elements via npm and CDNs. If both distribution methods are used on a page, one will error. npm usage can be directed to use scoped registries to avoid collisions.</li>
<li>Plug in systems. Plug-ins might bring their own custom element definitions which should not collide with the application or other plugins.</li>
</ul>
</section>
<section>
<h3>Concerns</h3>
<ul>
<li>---</li>
<li>Interaction with declarative shadow DOM (addressed)</li>
</ul>
</section>
<section>
<h3>Dissenting Opinion</h3>
<ul>
<li>---</li>
<li>None</li>
</ul>
</section>
<section>
Expand All @@ -588,7 +608,9 @@ <h3>Related Specs</h3>
<section>
<h3>Open Questions</h3>
<ul>
<li>---</li>
<li><a href="https://github.com/WICG/webcomponents/issues/914">[scoped-registries] Interaction with declarative shadow DOM #914</a></li>
<li><a href="https://github.com/WICG/webcomponents/issues/907">Scoped Custom Element Registry: Moving elements with shadow roots between documents #907</a></li>
<li><a href="https://github.com/WICG/webcomponents/issues/923">[scoped-registries] Element upgrade ordering #923</a></li>
</ul>
</section>
</section>
Expand Down