- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Thu, 28 Aug 2025 17:29:15 +0000
- To: public-css-archive@w3.org
I'm saying that the *CSS spec approach* of doing additive animations this way is a hack; reusing properties both as endpoints (normal property usage) and as deltas (different data type with different processing) is hacky, especially since you can't tell which mode they're being used in at keyframe definition time, only at *application* time. Additive animation isn't hacky in and of itself. I think it might indeed make sense to avoid enforcing min/max constraints while parsing @keyframes rules, because of this, and only go back and enforce them when actually applying the keyframes (as a normal animation). Or maybe we stick with the current behavior, and add a switch to `@keyframes` instead that declares the rule to be specifying deltas, which relaxes the parsing rules (so they're actually deltas) and makes them only usable as an additive animation. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12648#issuecomment-3234345013 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 August 2025 17:29:16 UTC