- From: vmpstr via GitHub <noreply@w3.org>
- Date: Thu, 14 May 2026 18:41:51 +0000
- To: public-css-archive@w3.org
Sorry for the delay I'd like to understand your use case a bit more. I presume that when you want to capture `::view-transition-group` of an ongoing scoped view transition, you mean to grab the pixels of whatever the current cross-fade view it currently holds as well as its geometry. Other than this, however, do you mean to cancel the existing scoped view transition and start a new transition with this as the starting state? Or am I misunderstanding where the new state is coming from? One of the unfortunate realities here is that if we _just_ remove the requirement, the implementation won't do what you expect. We need to revisit what it means to capture the state of an ongoing scoped view transition in a different view transition. There is separate ideas of making view transitions retargetable. Specifically, if you run a transition on the _same_ scope, then potentially it should use its in-progress transition state as the initial state of the second transition, which I think is what you're attempting to build. If true, then I would prefer we pursue the latter independently rather than attempting to loosen the view-transition-scope requirement -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13637#issuecomment-4453675619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 May 2026 18:41:52 UTC