Bronca

Newbies do things like that! ? I'll be attentiveness, thanks for all support bro!

To fire the animations after all the assets loaded: How to make animations and image load after the page is loaded - GSAP - GreenSock

@OSUblake I've found the culprit. Thank you for your support, i'm grateful. Take a look (I don't know why, but in Next.Js the window.onload before play animations common practice "locks" the timeline progress) : Just calling the function instead seems fix everything.

cocky-boyd-p6yk7 - CodeSandbox Oh man, this is so frustrating, the demo on CodeSandBox works! I don't have idea what's happening with my main code, is exactly the same thing.

Greetings, this is my first post in Greensock Forum. I've read the fixed topic, but if I'm doing something wrong even though let me know, okay? I've encountered a very tricky problem doing a Next.Js project with GSAP. I've created the Timeline and did all the animations I want. Everything works fine, but navigating between links make things harder, because when I push back one route (click back on the top of the browser) all animated elements of the page get their initial CSS setup. (In my case, visibility: hidden, so everything is gone!). In my mind the natural behavior of the page was keep the timeline final state, but this seems not occur. I know that is not a GSAP problem, but I'm wondering if anyone knows a way to workaround this behavior of React / Next.js. I tried restart the Timeline with UseEffect on router back, but no success.