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
I noticed that the wormhole content is rendered twice into the target during liquid fire transitions using liquid-outlet.
I think for transitioning from route1 to route2 liquid-fire has both pages prepared. That results in rendering the wormhole content of both pages into my header buttons area.
The text was updated successfully, but these errors were encountered:
Experienced as well, with Issue due to when using liquid-fire: both routes (transition to and transition from) are displayed on the screen while doing transform animations. Consquently the wormhole will display the new content and the old content at the same time until the transition is complete and the from route is destroyed.
I did animations with css. I‘ve created a wrapper component that can delay its destruction for the animation duration. Everything else was just a matter of switching css classes.
I should have done this from start because it was so much more productive. As you go from transition definition by custom js api to well-known standard css
I noticed that the wormhole content is rendered twice into the target during liquid fire transitions using liquid-outlet.
I think for transitioning from route1 to route2 liquid-fire has both pages prepared. That results in rendering the wormhole content of both pages into my header buttons area.
The text was updated successfully, but these errors were encountered: