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

@justinfagnani do you agree that having a low level primitive that allows us to do that is good enough? consider that it opens the door for others to rely on such primitive to do their own thing that doesn't necessarily requires the usage of a custom element, not everyone uses a custom element for everything in 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/782#issuecomment-455679952