- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Jun 2023 21:46:27 +0000
- To: public-css-archive@w3.org
> What do existing browsers do in cross document navigations to slow pages? Used https://foil-persistent-bookcase.glitch.me/page2.html for an example of navigation to a slow rendering page. When going to a new Document (same-origin navigation), all browsers are doing option 1 : "Keep the last frame from the old Document onscreen." When going back/forward, Chrome/Firefox do option 3: "Display cached rendering of the new Document" but Safari still does 1. > Also, does CSS define any of these concepts like old documents disappearing and new ones appearing? I would've imagined this should go in the html? Neither html nor CSS defines what should draw in the tab in the period between the navigation finishing and the new Document preparing its first frame. Since VT is standardizing cross-document transitions, makes sense for it to go in that spec but open to suggestions here. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8888#issuecomment-1590065456 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 June 2023 21:46:28 UTC