Re: [whatwg/xhr] setRequestHeader behavior doesn't seem to match implementations (#108)

So Fetch mentions `,` three times:

1. "combine"; used by XMLHttpRequest and WebSocket and brought up here.
2. "combined value", used by Headers. Unclear to me what we want to do there.
3. Population algorithm of the `Access-Control-Request-Headers` header. Unclear to me what we want to do there (I suspect nothing, but probably warrants a note, or maybe it should be refactored in terms of "combine").

So in part I'd like to know how much inconsistency we want here. We can go with what the majority does I suppose, but we'll have to add some notes here and there to explain that is what we're doing, since casual onlookers will find it weird.

-- 
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/xhr/issues/108#issuecomment-275654496