Scoped Custom Element Registries Are Baseline, Which Fixes the Two Widgets Problem

Web components have always had one awkward flaw: the custom element registry is global. If two scripts on the same page both try to define product-viewer, the second one throws an error. That happens more than you would think when a widget is embedded on a partner's site that already loads an older version of the same library.
Scoped custom element registries fix that, and with Firefox 159 they are Baseline newly available alongside Chrome and Edge 146 and Safari 26. You create a registry with new CustomElementRegistry(), define your elements in it, and attach it to a shadow root. Elements inside that shadow root use your registry, and the page's global one is left alone.
For studios that build embeddable things, such as 3D configurators, booking widgets or interactive maps that live on other people's websites, this is the change to adopt first. It means your component can ship its own versions of its child elements without caring what the host page has already registered.
Keep the global registry for your own site. Use scoped ones wherever your code is a guest.