Bug 33862 - [Chromium] Embedder initiated loads should not always stop existing loads
Summary: [Chromium] Embedder initiated loads should not always stop existing loads
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Darin Fisher (:fishd, Google)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-19 13:22 PST by Darin Fisher (:fishd, Google)
Modified: 2010-03-06 07:30 PST (History)
1 user (show)

See Also:


Attachments
v1 patch (2.24 KB, patch)
2010-03-05 14:18 PST, Darin Fisher (:fishd, Google)
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Fisher (:fishd, Google) 2010-01-19 13:22:26 PST
[Chromium] Embedder initiated loads should not always stop existing loads

For example, if navigating within session history to a reference fragment before the 'load' event runs, page loading should not be stopped.
Comment 1 Darin Fisher (:fishd, Google) 2010-03-05 14:18:44 PST
Created attachment 50120 [details]
v1 patch
Comment 2 Darin Fisher (:fishd, Google) 2010-03-05 14:19:44 PST
The point of this patch is to leave it up to the FrameLoader to decide when to stop any existing loads.  That matches the behavior of Safari (and other browsers).
Comment 3 WebKit Commit Bot 2010-03-06 07:30:47 PST
Comment on attachment 50120 [details]
v1 patch

Clearing flags on attachment: 50120

Committed r55626: <http://trac.webkit.org/changeset/55626>
Comment 4 WebKit Commit Bot 2010-03-06 07:30:51 PST
All reviewed patches have been landed.  Closing bug.