Re: [w3c/webcomponents] Add Scoped CustomElementRegsitry explainer (#865)

Feedback after debating this update with @diervo and @JanMiksovsky today:

1. Basic API looks good.
2. Inheritance is a convenience, otherwise complex apps will have to create big and probably expensive registries for the different buckets of components. (we can survive without it).
3. `getDefinitions` is a new capability that seems problematic, and unnecessary. up until now the web have survived without providing the list of built-in tags and their constructor. doing so for custom elements only seems weird, but we are more worry about someone having a way to inspect all defined elements, seems like a big footgun. We recommend remove that from the proposal for now.
4. `definitions` option is a convenience, but easy to do in user-land via subclassing. recommendation is to remove it from the MVP.
5. about "Note on looking up registries", we agreed that a dynamic lookup is sufficient.
6. about "Custom element constructors", we need to think about it, we agreed that only looking up on the global registry seems like a viable solution, and restrictive enough, but @JanMiksovsky want to think more about it (we will keep you posted).

-- 
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/pull/865#issuecomment-592863359