- From: Bramus via GitHub <noreply@w3.org>
- Date: Thu, 29 Jan 2026 16:48:54 +0000
- To: public-css-archive@w3.org
Playing around with this, I can come up with cases where I would want either behavior: 1. When I layer new (accumulating) animations onto the existing ones, I want the old ones to have an effect. Specific use-case: try and implement “Retargetable View Transitions” in userland 2. When I capture different elements in the two transitions that happen to have the same `view-transition-name` value, I don’t want the old animations to still have an effect in that case. Specific use case: in [this demo](https://view-transitions.chrome.dev/cards/spa/) the card that gets added to the list gets a fixed `v-t-name`. Admittedly the animations in the second scenario would be animations that are set to `composite: 'replace'`, so keeping the old animations around (and have them apply) wouldn’t have an effect anyway because the last animation replaces all preceding ones. In either case, authors can always loop over all animations attached to a pseudo, and cancel the manually if they want to. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13409#issuecomment-3818934074 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 January 2026 16:48:55 UTC