xaja

We dont see example, so cant say anything. “refresh” is a bad way. Something wrong. open dom inspector in your browser and try to see whats happen with dom tree when you change pages. By default you must see immediate update of dom tree

Once again. Did you check <transition>? Maybe you use nuxt, it uses transitions for default. It looks very similar with transition effect (even you dont see it)

yep. I just wrote this my previous comment so that people do not spend hours figuring out the basis of problem (like me :) in my case i even didnt have transition animations! i had <transition name="test"> without css. so i even didn't see delays between components changing but vue already worked differently...

I read all the articles on this and similar problems on this forum and on stackoverflow. and YES setTimeout working, but this is not the answer. I was also confused that the problem does not affect a large number of people, but they describe almost the same situations, when vue + router + gsap + scrolltrigger stops to work, when you go through the pages (routes) and return to previous one with animations (animations dont work in this case). so, guys, first of all look at <transition> above <router-view>. this is the problem, when you have components from previous page AND next page at the same time, and ScrollTrigger calculates the values (offsetTop) in that time