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
{{ message }}
Repository navigation
[animations] FadeThrough transition resets ongoing animations after FadeThrough page transition is complete #55874
I made this video to illustrate what I'm talking about.
In this extra slow-motion you can definitely see how spinners after making almost full circle just reseted to the initial animation due to extra renders
changed the title [-]Animations package, FadeThrought transition, extra renders[/-][+][animations] FadeThrough transition resets ongoing animations after FadeThrough page transition is complete[/+]on May 6, 2020
Hi @goderbauer
Thanks for your work.
I see that this ticket is closed by appropriate PR.
But this issue is still exists for me and all other users cause the was no release.
Do you have any info on the next release date?
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
vasilich6107 commentedon Apr 28, 2020
@TahaTesser, @shihaohong, @goderbauer
[-]Animations package, FadeThrought transition, extra renders[/-][+][animations] FadeThrough transition resets ongoing animations after FadeThrough page transition is complete[/+]vasilich6107 commentedon May 8, 2020
flutter/packages#141
is the right PR to follow while awaiting the fix
vasilich6107 commentedon May 30, 2020
Hi @goderbauer
Thanks for your work.
I see that this ticket is closed by appropriate PR.
But this issue is still exists for me and all other users cause the was no release.
Do you have any info on the next release date?
github-actions commentedon Aug 20, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.