fix(Transition): separate old vnode scope to avoid detached node is kept (fix #11782) #11789
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
close #11782
Initially tried to clean up
postClone
after it will no longer be used. But sincepostClone
is passed through all cloned hooks, it seems difficult to fix in that way.Instead, I have wrapped the area using old vnode with a block to avoid keeping
postClone
closure retains it. it is much simpler because we don't have to track cloned hooks norpostClone
is actually no longer needed.If there is better solution I don't notice, please let me know.