arturovt 75aeae42b7 fix(animations): cleanup DOM elements when root view is removed with async animations (#53033) ... Currently, when using `provideAnimationsAsync`, Angular uses `AnimationRenderer` as the renderer. When the root view is removed, the `AnimationRenderer` defers the actual work to the `TransitionAnimationEngine` to do this, and the `TransitionAnimationEngine` doesn't actually remove the DOM node, but just calls `markElementAsRemoved()`. The actual DOM node is not removed until `TransitionAnimationEngine` "flushes". Unfortunately, though, that "flush" will never happen, since the root view is being destroyed and there will be no more flushes. This commit adds `flush()` call when the root view is being destroyed. PR Close #53033		2024-01-25 16:32:57 +00:00
..
src	fix(animations): cleanup DOM elements when root view is removed with async animations (#53033)	2024-01-25 16:32:57 +00:00
test	refactor(core): node removal notifies scheduler only when animations are enabled (#53857)	2024-01-19 10:28:24 +01:00
BUILD.bazel	build: add missing entries for the api extraction (#52452)	2023-10-31 14:53:34 -07:00
index.ts	feat(animations): Add the possibility of lazy loading animations code. (#50738)	2023-09-29 10:49:39 -07:00
PACKAGE.md	feat(animations): Add the possibility of lazy loading animations code. (#50738)	2023-09-29 10:49:39 -07:00
public_api.ts	feat(animations): Add the possibility of lazy loading animations code. (#50738)	2023-09-29 10:49:39 -07:00