fix(overlays): tear down animations after dismiss #28907
Merged
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.
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?