- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Oct 2022 17:51:20 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts:
== [scroll-animations-1] What's the point of animation-range? ==
https://w3c.github.io/csswg-drafts/scroll-animations/#named-range-animation-declaration
> The [animation-delay](https://w3c.github.io/csswg-drafts/scroll-animations/#propdef-animation-delay) and [animation-range](https://w3c.github.io/csswg-drafts/scroll-animations/#propdef-animation-range) properties are both [shorthands](https://w3c.github.io/csswg-drafts/css-cascade-5/#shorthand-property) that set [animation-delay-start](https://w3c.github.io/csswg-drafts/scroll-animations/#propdef-animation-delay-start) and [animation-delay-end](https://w3c.github.io/csswg-drafts/scroll-animations/#propdef-animation-delay-end) together in a single declaration.
What's the point of having 2 shorthands if both have the same grammar and expand to the same set of longhands in the same way?
@cdoublev also confused in https://github.com/w3c/csswg-drafts/issues/7044#issuecomment-1252092947
@bramus said
> Otoh I do understand the need for animation-range: it is more readable in the content of scroll-linked animations. E.g. `animation-range: exit` is easier to grasp than `animation-delay: exit`.
But then maybe restrict `animation-delay` to `<time>{1,2}#` and `animation-range` to `[ <timeline-range-name> <percentage>? ]{1,2}#` or something?
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7901 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 October 2022 17:51:22 UTC