Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

Support for referrerpolicy attribute #424

Closed
pricop opened this issue Jul 18, 2016 · 2 comments
Closed

Support for referrerpolicy attribute #424

pricop opened this issue Jul 18, 2016 · 2 comments

Comments

@pricop
Copy link

pricop commented Jul 18, 2016

Are there any plans regarding the implementation of the referrerpolicy attribute to allow the control of referral value per item rather than per entire page, (using the meta referrer - which by the way still uses the legacy keywords rather than the new ones, see the Note mentioned here: https://w3c.github.io/webappsec-referrer-policy/#determine-policy-for-token)?

For example, I could load an image from a 3rd party website on a page, without the user's referrer to be sent out when the image request is made (https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-delivery).

The referrer policy draft is available at: https://www.w3.org/TR/referrer-policy/

Chrome already supports this.

@martinsuchan
Copy link

Even though the Platform Status shows Meta Referrer as supported, only the older draft is supported with values: never, always, origin & default
Edge should really support the current Editor's Draft on Referrer Policy, just like Firefox/Chrome/Opera.
See this issue for details:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7119603/

@pricop
Copy link
Author

pricop commented Sep 16, 2019

Since Edge has moved to the Chromium engine, this issue does not exist anymore.

@pricop pricop closed this as completed Sep 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants