- From: Christoph Päper via GitHub <noreply@w3.org>
- Date: Wed, 08 Oct 2025 05:58:39 +0000
- To: public-css-archive@w3.org
Those tables become easier to grasp if you put the additional effect in a separate column since it is (now) the same for all states. Keyword | Effect | _idle_ | _running_ | _paused_ | _finished_ | |-----|-----|-----|-----|-----|-----| |`play` |—| `play()` |—| `play()` | play() | |`play-once` |—| `play()` |—| `play()` |—| |`play-forwards` | +abs(rate) | `play()` | | `play()` | `play()` | |`play-backwards` | -abs(rate) | `play()` | | `play()` | `play()` | |`pause` |—|—| pause() |—|—| |`reset` | progress = 0 |—| `pause()` | ` pause()` | `pause()` | |`replay` | progress = 0 | `play()` |—| `play()` | `play()` | I have also found it helpful to describe behaviors by their deviation from either `play` or `pause`. From that, I wonder whether, for instance, `resume` or `unpause` would be a reasonable addition: it only has an effect when currently _paused_. -- GitHub Notification of comment by Crissov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12611#issuecomment-3379721618 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 October 2025 05:58:40 UTC