- From: Eric Portis <notifications@github.com>
- Date: Thu, 27 Sep 2018 14:35:22 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 27 September 2018 14:35:45 UTC
I'll add one concrete example of this not being clear to server-implementers – my employer, Cloudinary, implemented (and still implements) `Content-DPR` incorrectly. We echo back the DPR of the client, no matter how the width of the returned resource matches up with the requested `Width`. The example in section 4 could use some fleshing-out! Jeremey’s questions are all about describing how `Content-DPR` is actually used on the front end – I'll add that I think there should be more about how the server in the example calculated the `Content-DPR: 1` that it sends back. I assume that the resource it sent had a width of 160 pixels? That should be added to the example, along with a general formula that: `Content-DPR` should = response resource width, in pixels ÷ ( request `Width` ÷ `request `DPR` ) -- 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/812#issuecomment-425116482
Received on Thursday, 27 September 2018 14:35:45 UTC