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

`registry.run()` is an interesting idea... I'd have to think about ways it could break. It's similar to the patch of `.ownerDocument` I did for React.

One major difference is that in React we can figure out that the framework only creates elements with one specific API, and that it's not reentrant at the point of the patch. Here we'd have to make sure that all element creation APIs invoke the **Find a Custom Element Registry** step, and that we keep a stack of registries, _and_ we probably want to make this work across async DOM creation operations, so we may need to wait for something like [Async Context](https://github.com/tc39/proposal-async-context).

There may be bad cases where undefined elements are upgraded in the global scope because they're not defined in the custom scope and get upgraded in the adopt steps.

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

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