Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674)

The problem is that we wouldn't know when a custom element may be defined in the future. Since any definition can be added arbitrarily further in the future, there is no way to determine this.

This is yet another reason we opposed to the async definition of custom elements but since that ship has sailed, there's nothing we can do.

-- 
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/674#issuecomment-335319876