Re: [w3c/FileAPI] blob: slice() without valid content type yields unexpected results (Issue #177)

But `slice.type === ''`, correct? Isn't the behavior identical for blobs created with an explicit empty/non-valid contentType?

Don't your tests end up being more about what the [Fetch API returns for blob URLs](https://fetch.spec.whatwg.org/#scheme-fetch) when the Blob's type is an empty string? 

I haven't stared at Fetch enough, but it does seem inconsistent - _to get a header name_ should only return null if the header list does not contain the header, yet the "blob" fetch algorithm unconditionally appends Content-Type with the blob’s type. It may be that Fetch needs to define an attempt to parse the type, and on failure not append. Consider filing a bug against Fetch?


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/177#issuecomment-1167783124

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/FileAPI/issues/177/1167783124@github.com>

Received on Monday, 27 June 2022 19:23:07 UTC