fix(core): prevent duplicate nodes from being retained with fast animate.leave calls
#64592
+54
−2
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.
We were clearing duplicate nodes when both
animate.enterandanimate.leavewere on a node and were toggled quickly. We didn't account for this same situation, but when solelyanimate.leaveis present and rapid toggles occur. This ensures that thecancelLeavingNodesfunction is called in all cases instead of just enter animations.fixes: #64581