Re: [WICG/webcomponents] Lazy Custom Element Definitions (#782)

To reiterate with less words. Using promise and async is great, that it's not using callback too. If we can avoid adding complexity.

But, what about:
- ~add features. Like dependency injection.~ Context API to the rescue 🥳
- inject CSS (CSS variable definition, or any other Styling, Context API too?)
- Use our own element name (e.g. because the same component be used in different projects, when with legacy projects, and when we're migrating and keeping feature parity by replacing without having to change the generated HTML)


But I guess, besides the name, and handling registration at execution when promise is resolved.  All the rest can be done with Context API and DOM Events that the importing code can setup, listen to and handle.

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

Message ID: <WICG/webcomponents/issues/782/1523785431@github.com>