- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Jun 2023 16:12:41 +0000
- To: public-css-archive@w3.org
> @flackr What does that mean exactly? Isn't `auto` always effectively `0s` for time-driven animations? > > So it should be enough to say that the [resolved value](https://drafts.csswg.org/cssom/#resolved-values) is the computed value with `auto`s replaced by `0s` when `animation-timeline` is `auto`? (Otherwise resolved value = computed value). Yes, for time-driven animations (without group effects - which aren't shipped yet so we can defer on this part) this is enough. For scroll driven animations, it *should* be the resolved percentage. E.g. the value you'd get from `animation.effect.getComputedTiming().activeDuration`. However, given we don't support percentages as input to `animation-duration` I think returning `auto` for all other animations for now is reasonable. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6530#issuecomment-1577089761 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 June 2023 16:12:43 UTC