Closed Bug 1848743 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 41461 - invalid blob type should be equivalent to an empty type

Categories

(Core :: DOM: Networking, task, P4)

Product:
Core
Component:
DOM: Networking
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
119 Branch
Tracking Flags:
Tracking Status
firefox119 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Dan Robertson <drobertson@mozilla.com> wrote:

invalid blob type should be equivalent to an empty type

A Blob with a type that is a non-parsable MIME type should result in a empty content-type.

Related to: https://github.com/whatwg/fetch/issues/1693

Component: web-platform-tests → DOM: Networking
Product: Testing → Core

CI Results

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

Total 2 tests and 18 subtests

Status Summary

Firefox

OK : 2
PASS: 34
FAIL: 2

Chrome

OK : 2
PASS: 34
FAIL: 2

Safari

OK : 2
PASS: 34
FAIL: 2

Links

Gecko CI (Treeherder)
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/f632ab4abc0f [wpt PR 41461] - invalid blob type should be equivalent to an empty type, a=testonly https://hg.mozilla.org/integration/autoland/rev/7db869c3ff10 [wpt PR 41461] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/f632ab4abc0f
https://hg.mozilla.org/mozilla-central/rev/7db869c3ff10

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox119: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in before you can comment on or make changes to this bug.