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

One observation made during the F2F is that Firefox has an internal API that matches the alternative, a callback when a new element name is seen. Another observation was that this should likely coexist with scoped registries.

-- 
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-486823982

Received on Thursday, 25 April 2019 20:22:55 UTC