Re: [w3c/webcomponents] How to avoid memory leaks when detecting custom elements? (#674) from Joe Pea on 2017-10-10 (public-webapps-github@w3.org from October 2017)

From: Joe Pea <notifications@github.com>
Date: Mon, 09 Oct 2017 19:24:35 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/674/335340588@github.com>

> The problem is that we wouldn't know when a custom element may be defined in the future.

It doesn't matter because if a component is removed and no longer referenced ("destroyed"), then it should be able to destroy the expectation it had for a future element. It doesn't matter if the element is defined in the future or not, just that we clean the memory that was waiting for that future.

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

Received on Tuesday, 10 October 2017 02:24:57 UTC