Fetch is incompatible with multipart about bliss HOT 4 CLOSED

Doesn't headers: { "Content-Type": undefined } work?

from bliss.

It doesn't.

!env.headers["x"] doesn't distinguish between between passing a "falsy" x value or passing no x value.

If you want to enable, headers: { "Content-Type": undefined } you could replace the conditions with it with !("x" in env.headers) though.

I agree with you that this is a safer/less controversial approach in terms of compatibility. Do you want me to try it out and submit a PR?

from bliss.

Yes please! Thank you so much! 😀

from bliss.

Fixed in 7ee2577: You can now pass headers: {"content-type": undefined} ("content-type" being case-insensitive) to use the content-type set by the browser. I'll probably create another issue with a suggestion similar to #203 however (sorry @LeaVerou ;))

from bliss.