Re: [whatwg/fetch] Use case for Headers getAll (#973)

The WHATWG is working on standards for web browsers. To the extent other software wants to be compatible with web browsers, it's great to have their engagement. But if something does not sufficiently benefit web browser users then working on it elsewhere makes sense to me. It's totally up to them whether they want to be 100% compatible with a spec designed for web browsers, or add their own APIs. E.g. from what I understand most non-browser fetch implementations already ignore the CORS parts of the fetch spec and API.

Note that other browser engineers assessment of whether a proposal sufficiently benefits web browser users may be different than mine for any given proposal.

-- 
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/973#issuecomment-961231304