<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:mnot@mnot.net" title="Mark Nottingham <mnot@mnot.net>"> <span class="fn">Mark Nottingham</span></a>
</span> changed
<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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>mnot@mnot.net
</td>
</tr></table>
<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#c15">Comment # 15</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:mnot@mnot.net" title="Mark Nottingham <mnot@mnot.net>"> <span class="fn">Mark Nottingham</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=145380#c14">comment #14</a>)
<span class="quote">> > Case in point, if I'm opening a direct link to the image
>
> 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.</span >
You called the proposal "silly" twice in the same sentence -- is that really necessary?
<span class="quote">> 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 >
Content-DPR is a big win for servers and services that want to support responsive images without modifying HTML/CSS. Modifying response bodies has a server-side performance hit, and also introduces bugs.
Talking to various teams that work on Web Performance Optimisation products, this is very much a real problem; perhaps it's just not as visible to you.</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>