- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Jan 2024 20:48:49 +0000
- To: public-css-archive@w3.org
> Still need to review the PR but one quick comment based on this statement. > > > once when initiating the navigation, to check if a pageconceal event should be blocking > > The check should still be at 1 place after we have the final response. Because in the future it'll be based on the post redirect URL. We'll just run it in the browser (or parent process in Gecko?) to decide whether `pageconceal` needs to happen before VT capture steps. I hope this would become clearer with the HTML PR :) but in the meantime: We need to resolve the opt-in twice: once when the navigation is initiated and send that boolean to the browser process, and once right before `pageconceal`, given that it was blocking due to the opt-in being there when the navigation was initiated. We cannot read the opt-in directly in the browser process. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/9819#issuecomment-1899182140 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 January 2024 20:48:55 UTC