- From: Matt Perry via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Oct 2023 19:20:47 +0000
- To: public-css-archive@w3.org
In terms of use-case, thinking from the perspective of gestures and/or velocity-based animations, the very first problem I’ve had to solve with every animation library I’ve written is per-axis transform animation. I was surprised when transform/scale/rotate were implemented that they weren’t per-axis. For [Motion One](https://motion.dev), which is based purely on WAAPI, the approach has been via custom properties but of course these aren’t accelerated. They actually perform worse than the approach taken in [Framer Motion](https://framer.com/motion). This library constructs a new transform at the end of every animation frame but of course has to run on the main thread. Framer Motion uses WAAPI when values can be hardware accelerated and if transforms could be set per axis, many more animations would be. -- GitHub Notification of comment by mattgperry Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7646#issuecomment-1743619568 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 October 2023 19:20:49 UTC