[Webkit-unassigned] [Bug 16846] New: WebKit/gtk should probably create one FrameView for each page load

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 11 13:04:35 PST 2008


http://bugs.webkit.org/show_bug.cgi?id=16846

           Summary: WebKit/gtk should probably create one FrameView for each
                    page load
           Product: WebKit
           Version: 525+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: aroben at apple.com
                CC: alp at atoker.com


In r29369 <http://trac.webkit.org/projects/webkit/changeset/29369>, I changed
WebKit/win to start making one FrameView per page load like Mac does, instead
of one FrameView per Frame as we had previously been doing. This fixed a number
of bugs (listed in the ChangeLog for that commit), most of which only started
happening once the back/forward cache was enabled.

Bug 16822 discusses the desire to eventually just have one FrameView per Frame
on all platforms, but GTK may want to move to the multiple-FrameView model in
the meantime to avoid the bugs that Windows ran into.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list