Re: [fetch] 204 and json (#113)

I agree it's not something you'd want to do in general for all content types, but given that the decision has been made to have a `.json()` method - thereby elevating json above all other content types already - is it not reasonable to want it to behave a little more intelligently than a simple proxy to `JSON.parse()`?

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