Point mapping of <meta> referrer tag for the legacy 'default' to RP spec#5783
Merged
domenic merged 3 commits intowhatwg:masterfrom Dec 14, 2020
Merged
Point mapping of <meta> referrer tag for the legacy 'default' to RP spec#5783domenic merged 3 commits intowhatwg:masterfrom
domenic merged 3 commits intowhatwg:masterfrom
Conversation
domenic
requested changes
Aug 4, 2020
Member
domenic
left a comment
There was a problem hiding this comment.
You seem to have signed up to participate as an individual, but I believe you work in the field of web technologies, so were not able to sign that way. You can instead follow the instructions at https://sites.google.com/a/google.com/web-standards/home/standards-organizations/whatwg
domenic
approved these changes
Aug 5, 2020
Member
domenic
left a comment
There was a problem hiding this comment.
LGTM. Tagging as "do not merge yet" until w3c/webappsec-referrer-policy#142 gets merged, but I'm happy to merge when that lands. Great stuff!
Oh, also feel free to add your name to the Acknowledgments section if you'd like! See https://github.com/whatwg/html/blob/master/CONTRIBUTING.md#pull-requests for some more details.
Contributor
Author
|
@domenic w3c/webappsec-referrer-policy#142 has landed. Can we merge this now please? |
annevk
pushed a commit
to whatwg/fetch
that referenced
this pull request
Nov 30, 2020
w3c/webappsec-referrer-policy#142 links tests and has the corresponding Referrer Policy change. whatwg/html#5783 has the corresponding change to HTML.
Member
|
Still LGTM, but are there web platform tests for this specific change, i.e. for |
|
It looks like both |
Member
|
Ah OK. Can we get some coverage then, before we merge this change? |
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Dec 2, 2020
…licy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
This behavior is currently covered by a number of generated WPTs
(delivery type "meta" in the spec.src.json), but it doesn't cover a
handful of "legacy" keywords that the spec supports:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL adds test coverage for these keywords by adding new test cases
to referrer-policy/spec.src.json. It also incorporates a behavior change
proposed in a new spec pull request whatwg/html#5783,
which updates the "default" meta tag keyword to, instead of
being statically mapped to "no-referrer-when-downgrade" (which, until
recently, *was* the default policy), cross-reference the actual default
policy value. Finally, it removes a few now-redundant Blink web tests
covering the behavior the new WPTs verify.
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Dec 2, 2020
…licy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Dec 2, 2020
…licy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Dec 3, 2020
…licy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Dec 3, 2020
…licy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
pull bot
pushed a commit
to FreddyZeng/chromium
that referenced
this pull request
Dec 3, 2020
…licy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this pull request
Dec 5, 2020
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this pull request
Dec 7, 2020
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
sidvishnoi
pushed a commit
to sidvishnoi/gecko-webmonetization
that referenced
this pull request
Dec 10, 2020
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
sidvishnoi
pushed a commit
to sidvishnoi/gecko-webmonetization
that referenced
this pull request
Dec 10, 2020
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this pull request
Dec 14, 2020
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshigechromium.org>
Reviewed-by: Jeremy Roman <jbromanchromium.org>
Commit-Queue: David Van Cleve <davidvcchromium.org>
Cr-Commit-Position: refs/heads/master{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
UltraBlame original commit: 89d283f63157d10eb91f606a16cd1ec72302b99d
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this pull request
Dec 14, 2020
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshigechromium.org>
Reviewed-by: Jeremy Roman <jbromanchromium.org>
Commit-Queue: David Van Cleve <davidvcchromium.org>
Cr-Commit-Position: refs/heads/master{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
UltraBlame original commit: 89d283f63157d10eb91f606a16cd1ec72302b99d
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this pull request
Dec 14, 2020
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshigechromium.org>
Reviewed-by: Jeremy Roman <jbromanchromium.org>
Commit-Queue: David Van Cleve <davidvcchromium.org>
Cr-Commit-Position: refs/heads/master{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
UltraBlame original commit: 89d283f63157d10eb91f606a16cd1ec72302b99d
Contributor
Author
|
WPTs have been added in web-platform-tests/wpt/pull/26710 (thanks @davidvancleve !) |
Member
|
Awesome, thanks! Merging now. |
bhearsum
pushed a commit
to mozilla-releng/staging-firefox
that referenced
this pull request
May 1, 2025
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
bhearsum
pushed a commit
to mozilla-releng/staging-firefox
that referenced
this pull request
May 1, 2025
…> use the default referrer policy, a=testonly
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request whatwg/html#5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a companion to w3c/webappsec-referrer-policy/pull/142 which introduces a new
default referrer policyconstant in the referrer-policy spec. We should point the mapping of the legacydefaultreferrer policy specified via<meta>tags to the default value defined in that spec./infrastructure.html ( diff )
/semantics.html ( diff )