Intent to Prototype: Speculation rules referrer policy key
Kevin McNee
Explainer
https://github.com/WICG/nav-speculation/blob/main/triggers.md#explicit-referrer-policy
Specification
Work in progress. It will be added to https://github.com/WICG/nav-speculation.
Summary
This extends the speculation rules [1] syntax to allow developers to specify the referrer policy to use with speculative requests triggered by speculation rules.
[1] https://chromestatus.com/feature/5740655424831488
Blink component
Motivation
By default, the referring document's referrer policy is used for the speculative request. The use of a "referrer_policy" key in speculation rules allows the referrer policy to be set explicitly. For speculation actions that would be prevented by the "sufficiently-strict referrer policy" requirement [2] on a referring page with a lax policy, this allows the referring page to set a stricter policy specifically for the speculative request.
[2] https://github.com/WICG/nav-speculation/blob/main/fetch.md#stripping-referrer-information
Initial public proposal
https://github.com/WICG/nav-speculation/issues/167
TAG review
TAG review status
Pending
Risks
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
Web developers: No signals
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? No
Debuggability
In the DevTools Network tab, the speculative request can be selected to see referrer information.
Is this feature fully tested by web-platform-tests?
Yes
Flag name
SpeculationRulesReferrerPolicyKey
Requires code in //chrome?
False
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1355146
Estimated milestones
M110 for availability behind a flag.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4694585584910336
This intent message was generated by Chrome Platform Status.