- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jul 2023 20:39:48 +0000
- To: public-css-archive@w3.org
So I think there's a definitely nontrivial cost to adding these, in particular because it requires adding support for separately animating translate-x, translate-y, and translate-z, etc., on the compositor. If there are strong use cases for the splitting I think that complexity could be justified, but I don't think we should do this just "because a lot of other CSS properties do it", since I think it has significantly more implementation cost than for many other CSS properties. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7646#issuecomment-1646215265 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 July 2023 20:39:49 UTC