Previously we launched same-origin prerendering triggered by the speculation rules API. This expands coverage to also allow triggering same-site cross-origin pages. This prerendering will be done with credentials and storage access, but such prerender targets will need to opt in by using the Supports-Loading-Mode: credentialed-prerender header.
Prerendering is a useful technology for speeding up page loads, and ideally referrer pages would be able to prerender all target pages. By expanding the circle of prerenderable pages to include same-site cross-origin pages, we allow more navigations on the web to be instant.
Pending. (Review for this expansion was requested as a comment on an existing issues-mostly-addressed TAG review.)
This feature does not have significant interoperability or compatibility risks on top of the already-shipped same-origin prerendering feature. This is mostly a straightforward extension of that.
The only potentially-interesting questions are around the design of the Supports-Loading-Mode header, which is the main new web-exposed "API". We've designed the header with an eye toward being easily implementable and future-extensible, using the structured headers infrastructure.
Gecko: No signal. No signal on previous requests for prerendering and prefetching. I added a comment to the existing issue about prerendering.
WebKit: No signal. No signal on previous requests for prerendering and prefetching. I took this opportunity to re-file on their new GitHub repository in the hopes of getting some feedback.
Web developers: Positive. We've heard from a few partners that they want to prerender among other same-site origins they own, but cannot yet do so.
This feature is triggered by the speculation rules API.
Using this feature requires the target page to have some control over its HTTP headers. This is not possible on some free hosting sites, e.g. GitHub Pages. We have envisioned a future extension of allowing a <meta> version of Supports-Loading-Mode that could address this, but have not yet heard of a concrete case where this would be necessary, so it is not included in this Intent.
This feature respects the cross-origin-isolation process model, to prevent the referrer and target pages from attacking each other through side channels.
These issues are discussed further in the design doc and explainer.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
This feature is not available on WebView.
DevTools support for prerendering in general remains in the early stages; you can track that work in https://crbug.com/1217029, or see our general development guide.
However, this expansion to cross-origin same-site target pages does not have any special debuggability concerns.
Not yet, but we'll be writing such tests before shipping.
This intent message was generated by Chrome Platform Status and fixed up by hand.