<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Inconsistencies in main resource load delegates when loading from history"
href="https://bugs.webkit.org/show_bug.cgi?id=150927#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Inconsistencies in main resource load delegates when loading from history"
href="https://bugs.webkit.org/show_bug.cgi?id=150927">bug 150927</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=150927#c17">comment #17</a>)
<span class="quote">> I talked to Alexey about this yesterday. I believe his concern is that
> reordering the load delegates has the potential to break WK1 applications.
>
> We might need some setting to choose between the different behaviors?</span >
The order of the delegates is the same, set id, did receive response, data, finish. The difference is that set id and did receive response happens before the frame load is committed, like for all others loads. Do wk1 applications have special code to deal with history loads when page cache is enabled?</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>