Re: [fetch] typo in no-cors credentials handling (#169)

Hmm, until https://github.com/whatwg/fetch/commit/f334e0b2052076ea15eb39798c9e149290134878, it seems the `omit credentials flag` was only relevant when the mode is CORS. The direction we took was to introduce new combinations and make them useful?

I now agree that current spec is weird since `credentials mode` set to `omit` suppresses credentials even for `no CORS`, while `include`/`same-origin` has no effect for `no CORS`.

What's the potential use cases of no-CORS+same-origin combination? Jake's proposal contains it but I'm not sure whether or not it's written assuming that same-origin has no effect for no-CORS.
https://github.com/whatwg/fetch/issues/106#issuecomment-128735776

Currently no specific use case, but we should fix it so that `same-origin` + `no CORS` provides us new ability to us?

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/169#issuecomment-162024595