<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add Content-DPR header support"
href="https://bugs.webkit.org/show_bug.cgi?id=145380#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add Content-DPR header support"
href="https://bugs.webkit.org/show_bug.cgi?id=145380">bug 145380</a>
from <span class="vcard"><a class="email" href="mailto:ggaren@apple.com" title="Geoffrey Garen <ggaren@apple.com>"> <span class="fn">Geoffrey Garen</span></a>
</span></b>
<pre>Comment on <span class=""><a href="attachment.cgi?id=253706&action=diff" name="attach_253706" title="Patch">attachment 253706</a> <a href="attachment.cgi?id=253706&action=edit" title="Patch">[details]</a></span>
Patch
View in context: <a href="https://bugs.webkit.org/attachment.cgi?id=253706&action=review">https://bugs.webkit.org/attachment.cgi?id=253706&action=review</a>
<span class="quote">>> Source/WebCore/ChangeLog:9
>> + Spec: <a href="http://igrigorik.github.io/http-client-hints/#confirming-selected-dpr">http://igrigorik.github.io/http-client-hints/#confirming-selected-dpr</a>
>
> Which value wins when Content-DPR doesn't agree with image's internal metadata?
>
> I thought that most formats had that already, making duplication of the same functionality in HTTP harmful.</span >
"In case the server returned Content-DPR value contradicts previous client-side DPR indication, the server returned value must take precedence."</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>