Re: [whatwg/fetch] Should Body.formData() always strip the BOM? (#650)

The discussion above is about BOMs in `application/x-www-form-urlencoded`, which doesn't strip BOMs.
@eehakkin is going to change Chromium's behavior to align with the spec and Firefox (i.e. not to strip BOMs).

How about BOMs in `multipart/form-data`?
The spec https://fetch.spec.whatwg.org/#concept-body-package-data says

    Each part whose `Content-Disposition` header does not contain a `filename` parameter must be parsed into an entry whose value is the UTF-8 decoded content of the part.

So BOMs are NOT stripped in the spec. (Chromium strips BOMs, Firefox doesn't. See https://github.com/web-platform-tests/wpt/pull/17589)
What do you think about this case?

-- 
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/650#issuecomment-507450787