[BUG] Scroll-linked animation easing is broken - regression?

[kinglozzer]

These two items should move at different rates:
https://codesandbox.io/p/sandbox/scroll-triggered-animations-forked-h5jwk3

Appears to be a regression in v11.11 as it works in older versions (this is v11.10):
https://codesandbox.io/p/sandbox/scroll-triggered-animations-forked-7l3qwl

[xdanielc]

I noticed the same problem, this has been just for a week, so I'm understanding with it not being fixed yet

[xdanielc]

Ok, this is weird, I was using two elements on one animation to keep things more concise, I used your code and it worked, but then if you comment one (.one) element in the html, the element with the easing defaults to linear as far as I can tell.

I'm importing the more updated 12 version and motion, not framer-motion (althought both seem to exist)

https://codesandbox.io/p/sandbox/scroll-triggered-animations-forked-3ngrqh

Also I noticed that using x: [400, 0] instead of transform: ["translateX(400px)", "none"] makes the animation ease come back to linear as well, despite having the workaround of one invisible element.
I wonder how easy it will be to fix this given all unpredictable behaviour.

[RomanSmolka]

Same on my side. I've been fiddling with this for an hour and can't get easing to work inside scroll()
Version 12.3.1

[RomanSmolka]

I am pretty sure it happened with this change, where animation.flatten() is overriding the ease setting from animation options. Indeed downgrading to v11.11.15 (last version before this change), makes the problem go away. @mattgperry

[mattgperry]

I thought I wrote a comment about this somewhere, can't find it now, essentially there was a change made to make sure people didn't have to do this

scroll(
  animate(element, values, { ease: "linear" })
)

For the sensible scroll animation default, but I agree it should only happen if ease wasn't set by the user. I haven't had time to take a look yet but so you know this is on my list of priorities.