Re: [whatwg/fetch] FormData content-type doesn't match form submission behavior in browsers (#422)

> This is not very consistent with other Content-Type header values in the fetch spec.

Well, maybe those should be changed too?  ;)

> Is the issue related to breaking web sites?

Which issue?

The current situation, before the commits above is as follows:

1. Fetch spec says that sending FormData doesn't have a space there.
2. All browsers submitting HTML forms _do_ have a space there.  Changing this may or may not break websites; we simply don't know.
3. The HTML spec is consistent with the browser behavior.  See https://html.spec.whatwg.org/multipage/forms.html#submit-body the multipart/form-data case.

>From my point of view, all I want is that Fetch and HTML agree, so browsers can actually implement HTML on top of Fetch.  We can add the space to Fetch.  We can remove the space from HTML and make all browsers change longstanding form-submission behavior and hope there is no compat issue. The former seems much simpler to me, for what it's worth.

-- 
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/422#issuecomment-262993872