- From: Yoav Weiss <notifications@github.com>
- Date: Thu, 24 Oct 2019 00:30:00 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 24 October 2019 07:30:02 UTC
As long as different user agents support different file formats it doesn't make sense to align here.
For example, I think that nowadays Firefox and Chrome could align with each other, but they shouldn't align with Safari as long as Safari doesn't support webp and does support videos in image contexts.
What Fetch could do is provide general guidance about how UAs should construct their `Accept` strings (e.g. have the "rarest" supported format first, collapse commonly supported values into "*/*", etc), but I don't think the spec should dictate any specific values.
That is, unless we want to define precise processing ("if webp is supported, apng is supported, and video formats in image contexts are not supported, return ...." kind of definition).
Does that make sense?
--
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#issuecomment-545785423
Received on Thursday, 24 October 2019 07:30:02 UTC