<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Avoid evicting link preload resources when parsing is done."
href="https://bugs.webkit.org/show_bug.cgi?id=167415#c22">Comment # 22</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Avoid evicting link preload resources when parsing is done."
href="https://bugs.webkit.org/show_bug.cgi?id=167415">bug 167415</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=167415#c21">comment #21</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=167415#c20">comment #20</a>)
> > Comment on <span class=""><a href="attachment.cgi?id=299837&action=diff" name="attach_299837" title="Patch">attachment 299837</a> <a href="attachment.cgi?id=299837&action=edit" title="Patch">[details]</a></span>
> > Patch
> >
> > I guess an alternative would be to restrict m_preloads to speculative
> > preloads only.
> > Can we do that?
>
> We probably could, but that would probably mean duplicating the existing
> mechanisms that relate to m_preloads, or generalize them so that they can be
> applied to two separate lists. Do you think such a separation would be
> valuable enough to justify that?</span >
When I think about it some more, there are many cases where the same resource would end up in both lists, which will require deletion from one container before adding to the other. That's likely to add complexity, replace the simple list by maps, etc.</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>