- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 01:02:39 +0000
- To: public-css-archive@w3.org
> 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. Specs shouldn't have a concept of browser vs renderer process, this should be an implementation detail. This is the flow of events: 1. Navigation is initiated. 2. We have the final network response (in the browser process). If we're evaluating the opt-in after #2 but *before* dispatching any events to the page, which implementation option we choose below wouldn't be web observable: - The browser sends an IPC to the renderer to evaluate the opt-in. - The renderer replicates the renderer's CSS state in the browser. Do you see any issue with this? -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/9819#issuecomment-1905106765 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 January 2024 01:02:42 UTC