<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [link preload] Double downloads of preloaded CSS"
href="https://bugs.webkit.org/show_bug.cgi?id=169274#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [link preload] Double downloads of preloaded CSS"
href="https://bugs.webkit.org/show_bug.cgi?id=169274">bug 169274</a>
from <span class="vcard"><a class="email" href="mailto:yoav@yoav.ws" title="Yoav Weiss <yoav@yoav.ws>"> <span class="fn">Yoav Weiss</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=169274#c5">comment #5</a>)
<span class="quote">> Maybe you can track if the preload has been already been used and if so
> require full charset match (or reload)? Or maybe just reset the link-preload
> bit on the first match?</span >
Yeah, took that route and turned off the flag when reusing a charset mismatch.
<span class="quote">>
> A better, more complicated solution would be to support multiple charsets on
> CachedResource level. Clients would provide charset as a parameter on all
> accesses to decoded strings.</span ></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>