Closed Bug 1516310 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 14665 - [wpt/referrer-policy] Fix same-origin-downgrade in spec.src.json

Categories

(Core :: DOM: Security, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream][domsecurity-backlog])

Sync web-platform-tests PR 14665 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/14665 Details from upstream follow. Hiroshige Hayashizaki <hiroshige@chromium.org> wrote: > [wpt/referrer-policy] Fix same-origin-downgrade in spec.src.json > > Manual changes: spec.src.json. All others are generated. > > This caused two test files with the same contents with names > - same-origin-downgrade.http.html > - same-origin-upgrade.http.html > in directories under origin-when-cross-origin/. > This CL thus removes same-origin-downgrade.http.html without > affecting test coverage. > > (same-origin-downgrade is currently supressed by > source-https-unsupported-by-web-platform-tests-runners and thus > this CL doesn't add new files) > > Bug: 906850 > Change-Id: I1fcc150c4b2b643b3186cbef9432d343f8b4a1dd > > Reviewed-on: https://chromium-review.googlesource.com/1389925 > WPT-Export-Revision: 2144be146831a310b764bdca323f0eea55eaf673
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/d6e5517675a0 [wpt PR 14665] - [wpt/referrer-policy] Fix same-origin-downgrade in spec.src.json, a=testonly
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/0ea5f5f93dd0 [wpt PR 14665] - [wpt/referrer-policy] Fix same-origin-downgrade in spec.src.json, a=testonly
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.