- From: Bramus via GitHub <noreply@w3.org>
- Date: Tue, 17 Feb 2026 14:05:01 +0000
- To: public-css-archive@w3.org
> For same document transitions, you can already await inside the update callback before capture of new images runs, so there is no real gap there. The problem with delaying the update callback to complete is that rendering is blocked while the update callback is doing its thing. So ongoing animations that are irrelevant to the view transition would seem frozen. Compare the following two demos (click the document to start a View Transition): 1. `await` inside the `updateCallback`: https://codepen.io/bramus/full/YPWbEra/f4ec4d7967b7a7d61d1dacf326cd07fe 2. `await` after `t.ready`: https://codepen.io/bramus/full/NPxMvVE/45d641af16538a491532ca1dbcc1a741 Notice how in the first demo (which delays the fulfillment of the `updateCallback`) the dot on the right stops animating while the `updateCallback` is busy. In the second demo the dot keeps animating. _(Of course, if you were to block the capturing phase, then you’d still get that freezing behavior. It’s a tradeoff.)_ > I had understood `pagereveal` to imply that now is the time to dynamically configure view transitions and the next frame, including capture, follows immediately, rather than after an open ended pause. This would still be true. The proposed `waitUntil` would manipulate the ViewTransition object and then move on. The ViewTransition object itself can then delay the capturing or the playing of the animations. > I would find it cleaner if `<script blocking="render" type="module" async>` could somehow delay rendering not only for the synchronous part of the module, but also for any top level awaits. That seems like a larger change that could possibly have a much larger impact. It would also put same-document and cross-document view transitions on a diverging path. I’d rather see a solution that is similar for both types of view transitions, which the proposed `waitUntil` offers. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13013#issuecomment-3914881620 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 February 2026 14:05:02 UTC