So, Firefox 150 has added support for "Scoped CustomElementRegistry" (SCER for brevity) behind a flag (dom.scoped-custom-element-registries.enabled). I'm trying to figure out how this will solve the problem of micro-frontends bringing their own (i.e. different) version of a design system wc-library into a website. Are there any real world examples available yet? I mean deep dive blog posts or example repos that go beyond the Edge demo (of two confetti buttons 😉). I'm looking for answers to questions like - does the SCER only apply to custom elements being added within its shadow DOM? no light DOM then? - is it the React app's responsibility to create its own SCER, wrap itself into that shadow-dom and define its own version of custom elements being used? - as DS UI lib author, how do I make that process the least painful or transparent at best from a DX point of view for our consumers Maybe you can help out 🥹 @westbrook or @stuffbreaker or @sir_pepe https://developer.chrome.com/blog/scoped-registries?hl=en #webcomponents #designsystems