- From: Bramus via GitHub <noreply@w3.org>
- Date: Wed, 10 Sep 2025 16:49:10 +0000
- To: public-css-archive@w3.org
> I'd like to emphasize this. Now that there can [only be one active view transition at a time](https://github.com/w3c/csswg-drafts/issues/11292) the view transitions approach is even less feasible. #11292 was concerned with how to batch updateCallbacks. Even before that issue was discussed, you’d get only one active view transition. The new one would skip the old one. Note that the upcoming [Scoped View Transitions](https://github.com/WICG/view-transitions/blob/main/scoped-transitions.md) – now [available for testing in Chrome](http://developer.chrome.com/blog/scoped-view-transitions-feedback) – will allow multiple view transitions to run at the same time, as long as they have different scopes and don’t want to snapshot the same elements. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9500#issuecomment-3275735710 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 September 2025 16:49:11 UTC