- From: Noam Rosenthal via GitHub <noreply@w3.org>
- Date: Tue, 17 Feb 2026 17:06:51 +0000
- To: public-css-archive@w3.org
> 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. Right, but the second "capture" only matters for figuring out the participating elements via `view-transition-name`. You should be able to do this before an image is loaded, and use finer grained control over the animation. If this is only for cross-document and should affect *captures*, it should look different and work before the `pagereveal` event somehow. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13013#issuecomment-3915933294 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 17:06:52 UTC