<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#c14">Comment # 14</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:ap@webkit.org" title="Alexey Proskuryakov <ap@webkit.org>"> <span class="fn">Alexey Proskuryakov</span></a>
</span></b>
<pre><span class="quote">> Case in point, if I'm opening a direct link to the image</span >
Standalone images are a rare case, and it is always possible to solve any problems with those by embedding them in an HTML document. We do not need to add complicated features to the platform to enable silly approaches - making every possible silly approach fixable at some other level is not the goal.
Yes, it is always possible to advocate for addition of features with theoretical "what ifs" like this one, but new features should solve real problems, not provide an umpteenth way to solve a problem that's already solved.
<span class="quote">> You're successfully using it to negotiate gzip'ed versions of text assets on this very page;</span >
This is a transport level feature, so it is implemented at the correct level. There is no content negotiation going on in this case.
<span class="quote">> it's being used (very successfully) to negotiate and deliver various new image formats (e.g. WebP, JPEG-XR), and so on. It works.</span >
This is surprising if true. Negotiation of HTML vs. XHTML was a tragic failure.</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>