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

Yeah, can you list the scenarios?

I don't see how deeply nested elements would effect any API shape we've discussed though. Custom element registries are already invoked for any potentially custom element. This is how non-lazy definitions work. So in any case where an element would have potentially upgraded the registry could see a lazy definition and invoke whatever callback/event/Promise the API uses.

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

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

Received on Thursday, 27 April 2023 14:57:50 UTC