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

Good points! I think that addresses most of what I was proposing. But I think there are some other scenarios. In particular:

* What about the issue of first vs. successive appearances of the element? (I don't have any scenarios for this from my customers, but it seems worth considering.)
* What about when you may want to set up something like an IntersectionObserver on the actual element instance to determine when to load?

Seems like we might at least want the callback to receive the `HTMLUnknownElement` instance.

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

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