Unexpected stagger behaviour

[KerveCreative]

Hi. In the example codepen, I am expecting to see the white dots to stagger scale from 1 to 0, then once that animation has finished, scale from 2 + opacity 0 to scale 1 and opacity 1. Instead, it appears that the opacity is being set to 0 when the first animation is triggered. I have used the > timer marker to trigger the second animation after the first one has animated, which I would have thought would prevent the opacity being set to 0 until the second animation is triggered. Can anyone explain this behaviour and how to fix please?

See the Pen qBopQod by mattsnook (@mattsnook) on CodePen

[Cassie]

Hey there!

 

Welcome to the forums and thanks for being a Club GreenSock member. 🥳

 

'>' - this position parameter isn't needed as it's the default. When animations are added to a timeline, they'll play one after another.

 

However - you're using fromTo tweens which immediately render their starting values which is giving you unexpected results here

Give this a little watch/read through and it will all become nice and clear
 

 

 

[KerveCreative]

Fantastic, thanks for the quick response @Cassie. Now fixed.