Re: [whatwg/fetch] Determining MIME type of Request and Response objects (#1135)

Agreed that the wasm-spec behaviour sounds more logical, though I don't think this case was considered in the decision. It seems like Chrome respects the late-set header, Firefox doesn't, and Safari doesn't ship the API. I'd probably consider it more important that wasm and fetch match, though, so I wouldn't object to changing wasm if we can't change fetch.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1135#issuecomment-756743506