- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Nov 2022 20:28:31 +0000
- To: public-css-archive@w3.org
> I put both because reading `animation-delay: range-name` or even `animation-delay: first-range x% second-range y%` is really strange, it's not really a delay. Technically it is still a delay in the units of the timeline. I.e. in the same way that `animation-delay: 1s` delays a time-based animation until a certain time is reached, `animation-delay: contain` delays a view-timeline based animation until a certain scroll position is reached. I can see how there might be some confusion though. The main issue I can think of with just using `animation-delay` is that when given a single `<time>` value it only sets the start delay (to preserve compatibility with animations today), however when used with a `<range-name>` it would set both start and end delays. We could make `animation-delay: <range-name>` invalid, and so `animation-range: <range-name>` is the way to implicitly set both delay-start and delay-end to a particular range but otherwise developers can use the two value `animation-delay` property or set `animation-delay-start` and `animation-delay-end` directly. This might be a bit awkward but avoids any redundant properties and explains why the 1-value range-name version sets both start and end. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7901#issuecomment-1306148556 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 November 2022 20:28:33 UTC