Closed Bug 1786775 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 35593 - [beacon-api] Allow non-CORS-safelisted content-type with preflight requests

Categories

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

task

Tracking

(firefox106 fixed)

RESOLVED FIXED
106 Branch
Tracking Status
firefox106 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Ming-Ying Chung <mych@chromium.org> wrote:

[beacon-api] Allow non-CORS-safelisted content-type with preflight requests

According to offline discussion with yhirano@, the spec implies
that we should follow Fetch's spec which allows beacon with non-CORS-safelisted content-type that requires preflight requests.

Bug: 1352366,1293679
Change-Id: Ic3c876a5226bd855098c5fb1e9114138fca6cd50
Reviewed-on: https://chromium-review.googlesource.com/3845374
WPT-Export-Revision: 90cae5101354d1879674d0e51e318bac116b5c68

PR 35593 applied with additional changes from upstream: 74938560647321aed597aa158a4bff731edbd759, f1ef84ca14e9e7f18d82544dfa2191ccab027757, 132606abb6068abac3aad510ede995caa37032de, ac84adaa5a4190f4937db37882ba1e3f00511c68

CI Results

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

Total 8 tests

Status Summary

Firefox

ERROR: 8

Chrome

ERROR: 8

Safari

ERROR: 8

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/46773be4c6ac [wpt PR 35593] - [beacon-api] Allow non-CORS-safelisted content-type with preflight requests, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in before you can comment on or make changes to this bug.