- From: pweis88 <notifications@github.com>
- Date: Tue, 01 Nov 2022 22:09:07 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 2 November 2022 05:09:19 UTC
> We're now looking to expand this to cover cross-origin same-site prerendering, i.e. cases like `https://a.example.com/` prerendering `https://b.example.com/`. This _will_ include credentials/storage access, since those are site keyed, but it will also require an opt-in from the target site via a new HTTP response header, `Supports-Loading-Mode: credentialed-prerender`, to protect the origin security boundary. We're exploring different use cases for prerendering in Google Workspace apps that would require cross-origin same-site support. This is generally needed for cross-app user journeys, a good example of which is prerendering of Google Docs documents (docs.google.com) that users are likely to navigate to from e.g. Drive (drive.google.com) or Gmail. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/721#issuecomment-1299579222 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/721/1299579222@github.com>
Received on Wednesday, 2 November 2022 05:09:19 UTC