Re: [WICG/webcomponents] Scoped Custom Element Registries (#716)

> Additionally, I'd love to hear how folks are solving for their scenarios while waiting for this to land.

Using FAST, I implemented a feature we dubbed "scoped components" that let's our consumers register the same components multiple times using different prefixes. This isn't a proper solution, but it's the best we could do given what's currently available. (The proposed spec seems too early and complex to even think about polyfilling.)

I had to do this to support legacy architectures that do things that web apps arguably shouldn't do. Despite that, the requirement for _some_ kind of custom element scoping is very real in enterprise systems, and I see it being a blocker for widespread adoption on that front unless there's a reasonable solution for it.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/716#issuecomment-1137882457
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/716/1137882457@github.com>