You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This proposal allows for multiple custom element definitions for a single tag name to exist within a page.
This is accomplished by allowing user code to create multiple custom element registries and associate them with shadow roots that function as scopes for element creation and custom element definitions. Potentially custom elements created within a scope use the registry for that scope to perform upgrades. New element construction APIs are added to ShadowRoot to allow element creation to be associated with a scope.
This comment was automatically generated based on the information you provided. Please don't edit it.
Below is additional information about the web feature (from the web-features project) which is referenced in your proposal.
If this doesn't accurately correspond to your proposal, please update your initial comment to include web-features: <feature-id>.
To find feature IDs, use the web-features explorer.
Feature Scoped custom element registries
ID: scoped-custom-element-registries
Name: Scoped custom element registries
Description: The CustomElementRegistry() constructor creates a new custom element registry that's separate from the global window.customElements registry. Creating more than one registry is useful for multiple custom elements that have the same tag name to coexist.
Activity
github-actions commentedon Sep 5, 2025
This comment was automatically generated based on the information you provided. Please don't edit it.
Below is additional information about the web feature (from the web-features project) which is referenced in your proposal.
If this doesn't accurately correspond to your proposal, please update your initial comment to include
web-features: <feature-id>.To find feature IDs, use the web-features explorer.
Feature Scoped custom element registries
CustomElementRegistry()constructor creates a new custom element registry that's separate from the globalwindow.customElementsregistry. Creating more than one registry is useful for multiple custom elements that have the same tag name to coexist.yulunwu2 commentedon Nov 21, 2025
https://wpt.fyi/results/custom-elements/registries?label=master&label=experimental&aligned&q=custom-elements%2Fregistries
dandclark commentedon Jan 28, 2026
Looking at the tests under https://wpt.fyi/results/custom-elements/registries, all are related to scoped custom elements registry except for these, which only deal with the global registry:
So a good test list would be https://wpt.fyi/results/custom-elements/registries excluding those 6 tests.
wpt-interop commentedon Feb 12, 2026
Thank you for proposing Scoped custom element registries for Interop 2026.
We are pleased to let you know that it has been accepted as part of the Scoped custom element registries focus area.
You’ll be able to track progress on this topic throughout the year via the Interop 2026 dashboard.
Posted on behalf of the Interop team.