Summary: | [Chromium] Embedder initiated loads should not always stop existing loads | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Darin Fisher (:fishd, Google) <fishd> | ||||
Component: | WebKit API | Assignee: | Darin Fisher (:fishd, Google) <fishd> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | commit-queue | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Darin Fisher (:fishd, Google)
2010-01-19 13:22:26 PST
Created attachment 50120 [details]
v1 patch
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 on attachment 50120 [details] v1 patch Clearing flags on attachment: 50120 Committed r55626: <http://trac.webkit.org/changeset/55626> All reviewed patches have been landed. Closing bug. |