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

Revisiting this after [feedback](https://dev.to/ryansolid/web-components-are-not-the-future-48bh) from @ryansolid on how WCs add extra work for framework authors… This seems like a case where we may want to reconsider the current approach.

[This part of the spec](https://github.com/WICG/webcomponents/issues/1043#issuecomment-1883480452) would effectively force frameworks to replace current usages of `document.createElement` and `document.importNode`, which is a big ask. 

Meanwhile, Salesforce has (I believe) the largest deployment of a scoped custom element registry polyfill, and our approach is not based on this design at all but rather on something closer to `registry.run()`, which is (AFAICT) compatible with how frameworks currently work, since it just implies that `document.createElement` et al means something different when running in the registry context.

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

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