- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Aug 2023 14:21:35 +0000
- To: public-css-archive@w3.org
> Correct me if I'm wrong, but I don't think the spec (html or css) is opinionated whether the visual buffer has to remain uncleared for any duration. We had a resolution for this at https://github.com/w3c/csswg-drafts/issues/8888. The browser has to retain the contents of the old Document in the visual buffer until the new Document renders a frame when there is a transition. But now that you brought it up, I can think of one edge case where it might not be possible: "the process where the old Document's cached rendering was stored crashes". We can add spec text to say, "If the browser can not retain content from the old Document, the transition should be skipped" with a non-normative note clarifying this situation as an example for when that would happen. Does that suffice? -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9155#issuecomment-1669715900 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 August 2023 14:21:37 UTC