Re: [WICG/webcomponents] [scoped-registries] Consider future expansion to allow using a registry without new API (Issue #1043)

as a web component library author, i think a big part of this scoping use case is how to design/implement scoping so that frameworks don’t necessarily have to specifically opt in? if framework updates are required to support scoping, that means that only future applications or app updates can benefit. 

is it possible to implement a solution that works with the current `document.createElement` calls that frameworks make today so that frameworks don’t have to do anything and scoping just works out of the box?


i work on a web component design system library for primarily react consumers. that particular combination of framework + custom elements has been particularly difficult and consumers of the web components often use these kinds of things “not working in react” as negative feedback for web components instead perhaps of being negative feedback for react. 

the more features that browser can implement seamlessly without framework adoption the better imo. is there any path towards detecting the registry to use when an element is inserted into the document?


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

Message ID: <WICG/webcomponents/issues/1043/1882003402@github.com>