-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP Referrer-Policy - change to default #9303
Conversation
|
@ddbeck Thanks. I have added the new subfeature
But I don't understand the rest of the instruction, in particular
Point being if it isn't worth documenting one, I don't see why we'd document any as a compatibility thing. If this is worth doing, you're going to have to show me how. I don't understand how this could work in the schema. Sorry! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I misunderstood the default policy setting bug (I thought it was a way to opt-in into the new default, but that's exactly wrong). One small change needed here, then we'll be ready to go.
Co-authored-by: Daniel D. Beck <daniel@ddbeck.com>
Done. Thanks very much! I know it isn't compatibility, but finding a place for those default firefox preferences is tough. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! 🎉
The default HTTP
Referrer-Policy
changed fromno-referrer-when-downgrade
tostrict-origin-when-cross-origin
in Firefox 87 (https://bugzilla.mozilla.org/show_bug.cgi?id=1589074) as a result of this spec change: whatwg/fetch#1066. The change will also affect chrome and others.In addition, the MDN page has some notes about setting the default which I understand we'd now include in BCD (reproduced below):
This first draft just puts all of these things as notes . What I THINK needs to happen is that we have a new subfeature to indicate the version at which
strict-origin-when-cross-origin
is used as the default. So if this is false or unknown the assumption is that the default isno-referrer-when-downgrade
. Does that make sense? The other notes from the box above would then be re-worked without all the detail about the "default default" :-)Does that make sense? If so, any suggestions for the feature name and description?
@ddbeck Your advice appreciated.
Note, this impacts FF content update: mdn/content#2516