Re: [w3c/webcomponents] Scoped Custom Element Registry: Open Design Issues (#895)

_I tried to get docker working today but everyday is a new bug there_.

Unfortunately, I'm yet to re-render the specs to give another read and a better follow up, so my answer here is from my memory recollection.

> As far as I can tell you haven't taken any stab yet at how to modify the define() method to account for custom registries so it's hard to know what part you got stuck on.

Yes, this is a subtle change there, where I refer usage to the respective _object_. e.g. [here](https://github.com/leobalter/html/pull/1/files#diff-41cf6794ba4200b839c53531555f0f3998df4cbb01a4d5cb0b94e3ca5e23947dR66176).

That's why I added [this note](https://github.com/leobalter/html/pull/1/files#diff-41cf6794ba4200b839c53531555f0f3998df4cbb01a4d5cb0b94e3ca5e23947dR66389) clarifying the usage targets the given instance where the method is used in, and that could mean either the main `customElements` or other objects created by the user.

> The second concern really ties into adoption and associating a registry with a shadow root, neither of which seems to be covered in the draft text. (Most of that would probably end up in the DOM Standard.)

I tried to address this [out here](https://github.com/leobalter/html/pull/1/files#diff-41cf6794ba4200b839c53531555f0f3998df4cbb01a4d5cb0b94e3ca5e23947dR66356):

```
 Let document be this CustomElementRegistry's relevant global object's associated DocumentOrShadowRoot.
```

It's another subtle change, but I was trying to keep up with the observed prose.

---

My goal here is to start small, rather than trying to add too much. I'm not sure yet where I can improve it but I'll take a better look next week when I get through my current issue to run docker and render the page.



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