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
I noticed while while taking memory snapshots that some detached nodes where retained by runAfterTransition.ts.
🤔 Expected Behavior?
transitionsByElement should not retain any reference to nodes that have been removed from the DOM.
😯 Current Behavior
When a node with multiple transitions in progress is removed from the DOM a reference to it is still kept in transitionsByElement.
I think the problem is here. Only the first transitioncancel event is listened for and since there are still tracked transitions on the node it is not removed.
💁 Possible Solution
Potentially don't setup the transitioncancel event listener with once: true
🔦 Context
No response
🖥️ Steps to Reproduce
I'm not sure how to replicate this in a sandbox.
Version
3.35.0
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
OSX
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered:
Provide a general summary of the issue here
I noticed while while taking memory snapshots that some detached nodes where retained by runAfterTransition.ts.
🤔 Expected Behavior?
transitionsByElement should not retain any reference to nodes that have been removed from the DOM.
😯 Current Behavior
When a node with multiple transitions in progress is removed from the DOM a reference to it is still kept in transitionsByElement.
I think the problem is here. Only the first transitioncancel event is listened for and since there are still tracked transitions on the node it is not removed.
💁 Possible Solution
Potentially don't setup the
transitioncancel
event listener withonce: true
🔦 Context
No response
🖥️ Steps to Reproduce
I'm not sure how to replicate this in a sandbox.
Version
3.35.0
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
OSX
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered: