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
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)
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.
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 isv11.10
):https://codesandbox.io/p/sandbox/scroll-triggered-animations-forked-7l3qwl
The text was updated successfully, but these errors were encountered: