- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 May 2023 06:14:43 +0000
- To: public-css-archive@w3.org
> After some more thought, I don't think `animation-timing-function` should be deprecated in favor of something like `animation-easing`. They would serve different purposes, and there may be use cases for using them together like it's currently possible in Web Animations; it's the developer's discretion. Plus, I don't see an intuitive way one property can play both roles without overriding each other. I thought @graouts covered that in #6982. Currently, when `animation-timing-function` is specified on a (pseudo-)element, it gets applied to all the keyframes in animations resolved against that element that don't specify `animation-timing-function` themselves. `animation-easing`, when applied on a _(pseudo-)element_ would always become the effect-level (i.e. iteration) easing. When applied on a _keyframe_, it would be applied to they keyframe. i.e. there's no cascade from (pseudo-)element to keyframes. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8881#issuecomment-1569558451 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 May 2023 06:14:45 UTC