- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Sun, 23 Oct 2022 21:59:04 +0000
- To: public-css-archive@w3.org
ydaniv has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-animations][scroll-animations-1] using animation-range in animation shorthand instead of duration and delay == Since `animation-duration` has no meaning for scroll-linked animations, as noted [here](https://drafts.csswg.org/scroll-animations-1/#dom-scrolltimeline-scrolltimeline): > A [ScrollTimeline](https://drafts.csswg.org/scroll-animations-1/#scrolltimeline)’s [duration](https://www.w3.org/TR/web-animations-1/#dom-effecttiming-duration) is 100%. We could say that `<time>`-related values have no meaning in `animation` shorthand values. Instead, those require an `animation-range` value, also discussed in #7575. Currently, `animation-range` is defined as an alias of `animation-delay` here: https://drafts.csswg.org/scroll-animations-1/#named-range-animation-declaration. Perhaps we could define `animation` to either include `<time>` values for time-based animations, and have that resolve to `animation-delay` - which will in turn can be defined as only `<time>#`; or include only a `<timeline-range-name>#` - and then resolve to `animation-range`? Then we could also make these definitions mutually exclusive and also remove the confusion? FYI @fantasai @flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7944 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 23 October 2022 21:59:05 UTC