- From: Callum Law via GitHub <noreply@w3.org>
- Date: Tue, 09 Dec 2025 00:45:20 +0000
- To: public-css-archive@w3.org
Calme1709 has just created a new issue for https://github.com/w3c/csswg-drafts:
== [web-animations-2] Should CSSNumericValue number values be allowed for setting start and current time? ==
Both Chrome and WebKit support setting the start/current time of a time-based animation to a CSSNumericValue number value (i.e. `CSSNumericValue.parse("3000")`) and this is explicitly tested in WPT for both [current time](https://github.com/web-platform-tests/wpt/blob/58ef8ccbdef529f414c074fa57564cf88e7bf7f2/web-animations/timing-model/animations/setting-the-current-time-of-an-animation.html#L61) and [start time](https://github.com/web-platform-tests/wpt/blob/58ef8ccbdef529f414c074fa57564cf88e7bf7f2/web-animations/timing-model/animations/setting-the-start-time-of-an-animation.html#L29).
This is contrary to the spec which in [the procedure to validate a CSSNumberish time](https://drafts.csswg.org/web-animations-2/#validating-a-css-numberish-time) only allows CSSNumericValues with duration units:
>If all of the following conditions are true:
- The animation is not associated with a progress-based timeline, and
- time is a CSSNumericValue, and
- the units of time are not duration units:
throw a TypeError.
return false.
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13196 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 December 2025 00:45:21 UTC