Re: [csswg-drafts] [css-view-transitions-2] Extend `waitUntil` so that it can delay the start of the View Transition (animating phase) (#13013)

Yes, you are both right. Most of the time we want to keep the render freeze as short as possible. If, at capture time, all properties except the image content are present (and yes, image sizes should be statically known), you can probably make do with the old image, or take advantage of the fact that the new image is live and delay the animation after ready until the content has loaded.

The only mechanism I know for timing the second capture is blocking="render" on scripts, styles, and expect links. Rather than advocating more blocking, my point was that, for cross-document view transitions, I would like finer, programmatic control in the cases where it makes sense. Even though it initially seemed odd to me for the reasons mentioned, something like e.viewTransition.waitUntil(promise, { phase: "capture" }) would be welcome, if that is the direction to take.

-- 
GitHub Notification of comment by martrapp
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13013#issuecomment-3915880369 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 16:55:41 UTC