- From: Yoav Weiss <notifications@github.com>
- Date: Wed, 06 Apr 2016 05:14:52 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Wednesday, 6 April 2016 12:15:20 UTC
During recent [Chrome patch discussions](https://codereview.chromium.org/1839473002/#msg56), concerns were raised that Chrome's `Accept` headers are not spec compliant, as they include MIME types supported by Chrome but not supported universally. While that's not the case, it required explanations as to why our current implementation is as it should be. I think a note in the spec would go a long way to prevent similar cases in the future. This was [raised](https://github.com/whatwg/fetch/issues/43#issuecomment-98877690) in the past, but was concluded as unnecessary. I agree with past arguments that current spec language permits UAs to extend the `Accept` header, but stating it explicitly, saying that user agents may (or even should) extend the spec's values with MIME types they support, would be helpful. /cc @igrigorik --- 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/274
Received on Wednesday, 6 April 2016 12:15:20 UTC