- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Nov 2022 21:33:43 +0000
- To: public-css-archive@w3.org
> It doesn't matter if it's a use case or not, the behavior needs to be defined. Yes, what I mean is that IMO these cases, where length is applied to time-based animations and time applied to length-based animations, should be treated as invalid and ignored. - If the animation has a timeline that's length-based then it should only accept length values - ignore duration and delay and only accept ranges. - If the animation is time-based, i.e. `animation-tlmeline` resolved to `auto`, then it should only accept time values as it does now, and ignore ranges. This should also remove ambiguity from `animation-delay` and resolve the confusion with `animation-range` which currently only serves as an alias. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7575#issuecomment-1301315874 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 November 2022 21:33:45 UTC