A blob created from a fetch response does not correctly get type set

By design Issue #12009681

Details

Author
Josh H.
Created
May 13, 2017
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Steps to reproduce:

Fetch a file with header Content-Type: text/css; charset=utf-8

Actual results:

Blob type is set to text/css; charset=utf-8

Expected results:

Blob type is set to text/css

Reduced test case:

https://bl.ocks.org/jhabdas/87f8bc3573cf91b4c35e0c799addd762

Attachments

0 attachments

    Comments and activity

    • FWIW, I don’t agree here. The fetch spec suggests the content-type should be passed through directly. Gecko and Edge expose the charset parameters. Webkit and Blink sometimes expose them depending on their source, but sometimes strip them. Personally I think removing the sometimes-stripping behavior of webkit/blink would be the shortest path to cross-browser compat.

      More discussion of this here:

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

      And here:

      https://github.com/whatwg/fetch/issues/540

    • Previous comment is from bkelly at mozilla. Not sure why it shows me as anonymous.

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Brandon M.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “By design”

    • Thank you for filing this bug Josh! It appears that Chrome has a bug to move towards Edge and Firefox’s behavior which can be found here: https://bugs.chromium.org/p/chromium/issues/detail?id=724433. That said, I’m resolving this as by design. Thank you!

    You need to sign in to your Microsoft account to add a comment.

    Sign in