[Webkit-unassigned] [Bug 150927] New: Inconsistencies in main resource load delegates when loading from history
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Nov 5 05:14:19 PST 2015
https://bugs.webkit.org/show_bug.cgi?id=150927
Bug ID: 150927
Summary: Inconsistencies in main resource load delegates when
loading from history
Classification: Unclassified
Product: WebKit
Version: WebKit Local Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Page Loading
Assignee: webkit-unassigned at lists.webkit.org
Reporter: cgarcia at igalia.com
CC: akling at apple.com, cdumez at apple.com, darin at apple.com
Blocks: 142375
The order in which load delegates are called when loading a resource from history is different if the page cache is enabled or not. When the page cache is disabled, the order is the same to any other resource loaded from the network, but when the resource is loaded from the page cache, all the delegates are called after the load is committed. This has always been a problem for the GTK+ port (see bugs #91482 and #91478, for example), and I ended up trying to workaround the issue with messy code in WebKitWebView that is still causing us a lot of problems, see bug #142375. So, basically we are trying to ensure we always have a main resource with a response when the load is committed, that's something our API claims, and what applications expect. We have tried to solve this problem without affecting the WebCore behaviour, but it has caused more problems, and I think WebCore loader should be consistent in any case, so i think it's time to fix it in WebCore and remove all our hacks in GTK+
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151105/cd5c1b2a/attachment.html>
More information about the webkit-unassigned
mailing list