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
In the followed situations, some expected detached event(s) not fire:
[v-if] > [v-repeat] > [template] > [v-component]: In this structure, if we make [v-if] false after dynamic adding more components, the detached event won't be fired on the added components. demo
[v-repeat] > [template] > [v-component]: In this structure, if reduce the repeat items, it will destroy the redundant components. However it seems that it clears all detached events in _events before firing for the redundant components. It's worth noting that there are no problems for deeper components. demo
Test version: 0.11.5 ~ 0.11.7.
The text was updated successfully, but these errors were encountered:
Case 1 has been fixed in the transclude-refactor branch.
Case 2 is a bit different, because v-events and events option both only works when the instance is still active. When you set total=0, all instances are destroyed and the event listeners also. This also means it's not recommended to use the event system to listen to the internal lifecycle hooks.
In the followed situations, some expected detached event(s) not fire:
[v-if] > [v-repeat] > [template] > [v-component]
: In this structure, if we make[v-if]
false after dynamic adding more components, the detached event won't be fired on the added components. demo[v-repeat] > [template] > [v-component]
: In this structure, if reduce the repeat items, it will destroy the redundant components. However it seems that it clears all detached events in_events
before firing for the redundant components. It's worth noting that there are no problems for deeper components. demoTest version: 0.11.5 ~ 0.11.7.
The text was updated successfully, but these errors were encountered: