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

What I'll do for my un-named custom elements that I wants users to name, is to give them specific API for that, so `SomeElement.define('any-thing')`, `OtherElement.define('any-element')`, etc. By doing this, I can map constructors to names (rather than other way around with `customElements.get()`) so I can at least leak Promises only to the specific names for my classes.

In this case, if the elements are never defined, then there's something wrong, and I can throw a warning or error after a timeout.

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