Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058)

This seemed worth capturing after discussion with @justinfagnani. I believe the idea here would essentially additionally augment the steps to [lookup a custom element definition](https://html.spec.whatwg.org/#look-up-a-custom-element-definition) similar to how the [scoped registry proposal does](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md#finding-a-custom-element-definition) so when shadowRoot creation methods are called.

And in the strawperson-ing spirit, this would be something like:

~~3. Let registry be document's relevant global object's CustomElementRegistry object.~~

```
3. Let registry be...
  a. the last registry on the `runWithScope` registry stack
  b. or if that is null, the registry of the creating context's root node's registry
  c. or if that is null, the document's relevant global object's CustomElementRegistry object.
```

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

Message ID: <WICG/webcomponents/issues/1058/2105052703@github.com>