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

I don't see how this is possible without new API that frameworks use. Ideally frameworks would be flexible enough to show customization of what object/method they use create elements.

The fundamental proven is that existing `document.createElement` calls do not have enough information to determine a scope of a framework is rendering into a shadow root. There's no way for the platform to determine that either.

I've been able to get React working by patching `ownerDocument` of the container it's rendering into to return an object that overrides `createElement`. It's a hack, but I think shows that it would be pretty easy to use a scoped API at that point. Hopefully with little downside to a change, frameworks would accept PRs to used scoped creation APIs when present.

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

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