- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Mon, 16 Mar 2026 11:51:15 +0000
- To: public-css-archive@w3.org
My English proficiency fails me at the _pause_ state: Is it a result of a concluded action like `stopped`, which would imply `paused`, or is it a progressing action itself like `running`, which would imply `pausing`? I assume the former unless you could provide a duration for the pause. ---- If `image-animation` became a shorthand in the future, its current keywords could expand to longhands (e.g. including `image-animation-speed`, `image-animation-range`, `image-animation-timeline`, `image-animation-repeat`): - `normal`: `…-speed: 100%; …-range: 0% 100%; …-timeline: auto /*document*/; …-repeat: auto;` - `running`: `…-timeline: self /*element*/;` - `paused`: `…-speed: 0%;` - `stopped`: `…-speed: 0%; …-range: 0%;` This could suggest additional predefined values like: - `ended`: `…-speed: 0%; …-range: 100%;` - `reversed`: either `…-speed: -100%;` or `…-range: 100% 0%;` - `once`: `…-repeat: none /*no-repeat*/;` - `queued`: `…-speed: auto; …-timeline: sequential;` Since the range values should have `start` and `end` keywords and zero playback rate could be called `still` for readability and disambiguation, this would lead to interesting equivalencies, assuming that `normal` sets to defaults: - **`running`** = `self` or `element` - **`paused`** = `still` - **`stopped`** = `still start` - `ended` = `still end` - `reversed` = `end start` - `once` = `no-repeat` - `queued` = `sequential` That is just a thought experiment, of course. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13434#issuecomment-4067106058 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 16 March 2026 11:51:15 UTC