> Would you be able to use the disconnectedCallback() to trigger the disconnected event? Yep, you can. But it would be nice not to have to imperatively unsubscribe (see the article) - plus that's only internal to the component. The framework already does this btw (emit an event in `disconnectedCallback`) but it would be nice if it didn't have to. > Async event? We certainly don't want to add a synchronous event. That kind of DOM mutation events is exactly what we're trying to get rid of due to a high rate of security vulnerabilities caused by them and performance problems they cause. Given `disconnectedCallback` is already there, wouldn't this just be some sugar? Or are you suggesting to get rid of `disconnectedCallback`? -- 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/678#issuecomment-340734274
Received on Tuesday, 31 October 2017 11:26:48 UTC