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
Which @angular/* package(s) are the source of the bug?
animations
Is this a regression?
No
Description
I'd like to have an :enter animation for the new route (the previous component should be instantly removed), but when I have an element with :leave animation in the previous component, it stays in place till the new route animates in.
Please provide a link to a minimal reproduction of the bug
The home route has a list rendered.
Navigating to the about page animates in the element below the home and then the home disappears.
The about route does not have a list rendered.
Navigating back to the home page removes the about page instantly and animates in the home page.
Please provide the environment you discovered this bug in (run ng version)
@Totati Hi ,
For those who might encounter this issue:
This seems to be the expected behavior (same issue with v19). But here is a workaround. Adding an invisible transition with an adapted duration prevent the void between components.
Which @angular/* package(s) are the source of the bug?
animations
Is this a regression?
No
Description
I'd like to have an
:enter
animation for the new route (the previous component should be instantly removed), but when I have an element with:leave
animation in the previous component, it stays in place till the new route animates in.Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/stackblitz-starters-nldvyd
Reproduction:
The
home
route has a list rendered.Navigating to the
about
page animates in the element below thehome
and then thehome
disappears.The
about
route does not have a list rendered.Navigating back to the
home
page removes theabout
page instantly and animates in thehome
page.Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: