Fetch Web API - Content-type parsing

[MayyaSunil]

Description

The Fetch API is a very popular standard WEB API. Although this has been implemented by the major browsers from a very long time, we still have compat issues with regard to content-type parsing.

Specification

https://fetch.spec.whatwg.org/

Open Issues

No response

Tests

https://wpt.fyi/results/fetch/content-type?label=master&label=experimental&aligned

Current Implementations

• Blink
• Gecko
• WebKit

Standards Positions

No response

Browser bug reports

• https://bugs.webkit.org/show_bug.cgi?id=192000

• https://bugzilla.mozilla.org/show_bug.cgi?id=1510180

• https://bugs.chromium.org/p/chromium/issues/detail?id=908765

Developer discussions

No response

Polls & Surveys

No response

Existing Usage

No response

Workarounds

No response

Accessibility Impact

No response

Privacy Impact

No response

Other

No response

[dlrobertson]

Thanks for posting this! I too find content-type handling to be interesting.

Browser bugs from this comment:

• https://bugs.webkit.org/show_bug.cgi?id=192000

• https://bugzilla.mozilla.org/show_bug.cgi?id=1510180

• https://bugs.chromium.org/p/chromium/issues/detail?id=908765

[dkrecichwo]

A lack of full cross-browser support for keepalive and priority is also holding the Fetch API back:

https://bugzilla.mozilla.org/show_bug.cgi?id=1342484
https://bugzilla.mozilla.org/show_bug.cgi?id=1839319

[foolip]

cc @annevk

[gsnedders]

If the intention is just the web API, does wpt /fetch/api include everything relevant there @annevk?

[annevk]

I think so. There might be some other subdirectories that could be reasonable to include, such as /range. That wouldn't really address the issue OP raised though with regards to Content-Type.

[jgraham]

The scope here is specifically about content-type parsing. Apologies for the earlier confusion. The test link in the original post has been updated to reflect that: https://wpt.fyi/results/fetch/content-type?label=master&label=experimental&aligned

[karlcow]

@jgraham do you remember any webcompat issues created by content-type parsing differences?

[nairnandu]

Thank you for proposing Fetch Web API - Content-type parsing for inclusion in Interop 2024.

We wanted to let you know that this proposal was not selected to be part of Interop 2024. This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year, if necessary.

For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024!

Posted on behalf of the Interop team.