Do you have any idea why the spring curves are springing like crazy when changing the browser tab to the prototype — just all of them, not even when clicking them. Gives me nausea. Have seen it happen on devices some times, too.
Yeah. The new animation backend uses requestanimationframe which is paused by your browser on tab switch. If you switch back it tries to recover by speeding up. Not sure how I can work around that.
haha, that's kind of funny. I understand what's going on. Is that the same for all three animation engines?
The one in Framer 2 used css keyframes and didn't have that problem. So I think this is just a byproduct of doing it this way. But it's worth it.
I noticed a similar behavior with large retina images in the prototype. When the layers with these images load/appear for the first time, the browser is loading the image into the layer, which may cause some dropped frames (?) and then requestAnimationFrame is keeping up again? The spring curves wiggle stornger / more tension the first time during loading, but are correct on any subsequent show/hide/load