Re: [whatwg/fetch] "get, decode, and split" seems incorrect (#1068)

> Well, Content-Type in a way, as `text/html;charset="utf-8"` ought to work.

I don't think this example illustrates the issue. Get, decode, and split would preserve those quotes either way. Currently it only strips quotes at the beginning and end of a comma-separated segment.

I suspect there is nothing in the platform that actually consumes outputs from get, decode, and split where one of the list members is expected to start and end with a quote. (E.g., because that list member contains a comma.)

From another angle:

I agree that preserving quotes will make the existing parts of the platform work better. My concern was about a hypothetical part of the platform, e.g. some header whose value space was `x`, `y`, or `"z,w"`. Preserving quotes would work slightly worse for such a header. But, probably no such headers exist, and if they come to exist in the future, we'll deal with it.

-- 
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/1068#issuecomment-669321049