- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Oct 2023 18:58:33 +0000
- To: public-css-archive@w3.org
Quoting @birtles [on Twitter](https://x.com/brianskold/status/1708807450672148965): > Maybe we need to introduce translateX and translateY properties 😅 This was sparked by [a tweet](https://x.com/mattgperry/status/1708776364944331054?s=20) by author @mattgperry. For their framework [Framer Motion](https://www.framer.com/motion/), IUC, [they internally pipe the passed in `x`/`y`/etc. options to Custom Properties](https://x.com/mattgperry/status/1708809076707139918), which they then use to build a `transform` themselves. This has the downside of [not being hardware accelerated](https://www.bram.us/2023/02/01/the-gotcha-with-animating-custom-properties/). With translateX/translateY/etc. this would not be a problem, as Framer Motion could then pass these props straight into the individual transform properties. As Matthew put it in [a follow-up tweet](https://x.com/mattgperry/status/1708808880740859936): > Yes it would be amazing to be able to set each axis directly! -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7646#issuecomment-1743590364 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 18:58:35 UTC