Intent to Implement and Ship: referrer policy on Fetch API Request
Yutaka Hirano
Intent to Implement and Ship: referrer policy on Fetch API Request
Contact emails
Spec
https://fetch.spec.whatwg.org/
https://www.w3.org/TR/referrer-policy/
Summary
In general, referrer policy controls the referer HTTP header. It can be set to a document via CSP or <meta name="referrer"> element. It can be set to an individual element via an attribute. See Emily's intent-to-ship for details.
A Request object has referrerPolicy property, which represents its internal request's referrer policy. A developer can set the property via the Request constructor.
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Interoperability and Compatibility Risk
Firefox has implemented the property and is planning to ship it by 47. WebKit has implemented the property. Given that the interface change is not big and we've already shipped Element's referrer policy attribute, I think it's no problem to ship it for the Fetch API.
OWP launch tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=532385
Entry on the feature dashboard
Jochen Eisinger
Chris Harrelson
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
