- From: David A via GitHub <noreply@w3.org>
- Date: Tue, 24 Mar 2026 13:17:44 +0000
- To: public-css-archive@w3.org
> One (tiny, but important) thing about your example, it needs a / between the events as pointerdown / pointerup to be stateful: Right, thanks. > Regarding the OP, though the example is a bit contrived, you could think of an example with 2 buttons, which is more likely to occur: Yeah this seems like a valid example to me so I would support the proposal that play-forwards and play-backwards have no effect if the animation has already reached its end. > Another option I can think of is changing the whole model of "name-clashing" for triggers. Like Rob says, this does seem like a separate issue. I think we probably have a lot of options to handle multiple matching names, e.g. `animation-trigger: all(--trigger) play` to mean attach all, `animation-trigger: all --trigger play` alternatively, etc. -- GitHub Notification of comment by DavMila Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13643#issuecomment-4118212859 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 March 2026 13:17:45 UTC