You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
then when I call grandparent.destroy(), the destroy event is never triggered for the child. Is there a specific design reason for this? I'm running into children not removing themselves as listeners, even though I thought they were being destroyed.
To clarify further, I have bound a pre:destroy event inside child to make sure it cleans up after itself in the application. But since destroy isn't getting called, the cleanup doesn't happen.
The text was updated successfully, but these errors were encountered:
Hey @arturadib, I noticed that the destroy event isn't propagated to the children, so if I have a hierarchy like so
then when I call
grandparent.destroy()
, thedestroy
event is never triggered for thechild
. Is there a specific design reason for this? I'm running into children not removing themselves as listeners, even though I thought they were being destroyed.To clarify further, I have bound a
pre:destroy
event insidechild
to make sure it cleans up after itself in the application. But sincedestroy
isn't getting called, the cleanup doesn't happen.The text was updated successfully, but these errors were encountered: