You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
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)?
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.
The text was updated successfully, but these errors were encountered: