-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(overlays): tear down animations after dismiss #28907
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic work 👏
Co-authored-by: Liam DeBeasi <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job! I tested this in another app I was debugging, and it fixes one of the issues there as well.
Issue number: resolves #28352
What is the current behavior?
Not all animations are getting properly destroyed after they run. This means that styles can get stuck at the end value of their animation.
Specifically for this reproduction (as reported in the bug ticket), if the modal animates from 1 to 0 opacity and then the modal gets reopened with a different animation where the opacity should be 1 throughout (i.e. the opacity isn't supposed to animate at all), the modal is invisible because the opacity got stuck at 0 and never got reset to the default value of 1.
This bug is probably causing some incorrect behavior on other edge cases with overlays, but this is the only one I've identified.
Reproduction steps
Note: you cannot reproduce this when using a modalController
ios
mode on a screen wider than 768pxWhat is the new behavior?
Does this introduce a breaking change?