-
Notifications
You must be signed in to change notification settings - Fork 26.2k
fix(core): Flush animations when no component has been checked by CD #58089
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
Conversation
4564414
to
ebdda3b
Compare
ebdda3b
to
33c4811
Compare
33c4811
to
1b677c5
Compare
1b677c5
to
b6986ee
Compare
b6986ee
to
1b52af2
Compare
1b52af2
to
2741a92
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
2741a92
to
965054a
Compare
24ef696
to
3d34822
Compare
3d34822
to
47d7760
Compare
47d7760
to
1b82a35
Compare
5a26e95
to
1f17456
Compare
When Angular runs application synchronization automatically, animations are now guaranteed to be flushed, regardless of whether change detection was run on any components attached to `ApplicationRef`. This most frequently affects animations related to component removal where the DOM element for the component would previously not be removed due to animations not being flushed BREAKING CHANGE: Animations are guaranteed to be flushed when Angular runs automatic change detection or manual calls to `ApplicationRef.tick`. Prior to this change, animations would not be flushed in some situations if change detection did not run on any views attached to the application. This change can affect tests which may rely on the old behavior, often by making assertions on DOM elements that should have been removed but weren't because DOM removal is delayed until animations are flushed. fixes angular#58075
1f17456
to
07c2ae4
Compare
Green TGP (with local changes to fix tests). |
This PR was merged into the repository by commit 0b69b61. The changes were merged into the following branches: main |
fixes #58075