- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Feb 2023 22:03:09 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [scroll-animations-1] animation-range vs animation-duration == If `animation-range-start`, `animation-range-end`, and `animation-duration` are all set, and duration doesn't exactly match the available range, what do we do? Options proposed so far: * Ignore `animation-range-end`. * Ignore `animation-duration`. * Take the smaller duration. Related question: if `animation-duration` and `animation-range-end` are given but not `animation-range-start`, do we: * define the range as the normal timeline start through the specified range end? (pins the duration at the start of the timeline) * scope the animation to the given duration, pin it to the specified `animation-range-end`, and calculate the used value of `animation-range-start` accordingly? Fwiw, my original interpretation was that the `animation-range` properties each (independently) cut the timeline down to a particular segment, and then duration and delay play within that segment instead of within the whole timeline. An alternative view would be that `animation-range` is similar to `inset`, `delay` to `padding` or `margin`, and `duration` to `width`, and they operate as a set at the same time. Which worldview do we want to go with? (Or something else?) Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8405 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 February 2023 22:03:11 UTC