- From: Toru Kobayashi <notifications@github.com>
- Date: Tue, 14 Nov 2017 14:35:25 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 14 November 2017 14:35:51 UTC
Thanks! > There is no such a concept as "unmounting". Whatever library / framework that decides to make the template no longer work must manually remove event listeners, etc... Should we use custom elements or some component systems if we need those lifecycle concepts like mount〜update〜unmount? (Custom elements have `[connected|disconnected|...]Callback` and that is not a concern of template layer, it's a concern of component layer) > In general, there is not really a concept of deleting a subtree since everything JS can ever reach would always won't be collected by GC. Removing from a document, etc... wouldn't change this. Are template instances never released after they are created? I guess defined template type is never released but its instance will be released. I might be misunderstanding the following point. > yes, considering that the definition of a template type is global (or at the shadow level), and multiple instances are processed by the same template type processor, we need a way to disconnect these two pieces. -- 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/708#issuecomment-344277482
Received on Tuesday, 14 November 2017 14:35:51 UTC