Closed Bug 1634802 Opened 3 years ago Closed 2 years ago

[wpt-sync] Sync PR 23374 - Client hints: http-equiv accept-ch should not persist

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox78 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla78
Tracking Flags:
Tracking Status
firefox78 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 23374 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/23374
Details from upstream follow.

Maks Orlovich <morlovich@chromium.org> wrote:

Client hints: http-equiv accept-ch should not persist

Change-Id: I53e21a16d5e83590b99f6efb6d165d6a67336092
Reviewed-on: https://chromium-review.googlesource.com/2172586
WPT-Export-Revision: 1cf8787c24bbee26b1da7818e9f9418c787bb24f

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 3 tests and 3 subtests

Status Summary

Firefox

OK : 3
PASS: 9

Chrome

OK : 3
PASS: 9

Safari

OK : 3
PASS: 9

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/59894d4cd777
[wpt PR 23374] - Client hints: http-equiv accept-ch should not persist, a=testonly
https://hg.mozilla.org/integration/autoland/rev/ee2fbd0fd53e
[wpt PR 23374] - Update wpt metadata, a=testonly
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5b8e9d6a809a
[wpt PR 23374] - Client hints: http-equiv accept-ch should not persist, a=testonly
https://hg.mozilla.org/integration/autoland/rev/d80364ee9bfa
[wpt PR 23374] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/5b8e9d6a809a
https://hg.mozilla.org/mozilla-central/rev/d80364ee9bfa

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox78: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
You need to log in before you can comment on or make changes to this bug.