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

Traditional events have ways to clean up (`removeEventListener`), so it seems fair to need this for Promise-based APIs which are essentially future event notifications.

Maybe this is a more general problem for JavaScript. Maybe Promises returned from `.then()` simply need to be cancellable, just like ancient event mechanisms have ways to de-register event listeners.

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