- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 15:45:47 +0000
- To: public-css-archive@w3.org
> How would setting the iteration-wide easing inside a keyframe work? Would it reset the progress from that point? If not, what use-cases would that serve? It would not be a valid property inside a keyframe, like other animation affecting properties. > > So I think to do this we would have to have an `auto` value which would compute equivalent to linear except that it wouldn't trigger ignoring `animation-timing-function`. > > If we add another `auto` wouldn't that be a problem in the `animation` shorthand? If we used auto, I'd propose it is only specified through omission. > > For a slightly different proposal, we could treat animation-easing as a set-to-linear shorthand for animation-timing-function. > > I thought that was the initial proposal. You mean it would treat the `linear` value as "auto" until `animation-easing` is explicitly specified? I'm a bit confused here. If animation-easing is unspecified, then the animation easing will be linear (as it is today), and the animation-timing-function will have its default ease value unless another is specified by the developer. If the developer sets `animation-easing: linear` my thinking was that we would want to then replace the initial `animation-timing-function: ease` value with `animation-timing-function: linear` as well to respect the specified linear. This requires that the initial "linear" value and the specified "linear" value are handled differently. > Another option we can consider for solving the shorthand problem is using a new ["mode" property like I suggested above](https://github.com/w3c/csswg-drafts/issues/6982#issuecomment-1776756444). I'm not a fan of changing the interpretation of the timing function, but accept this may be the direction we have to go here. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6982#issuecomment-1854176600 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 15:45:48 UTC