[Webkit-unassigned] [Bug 13672] DumpRenderTree needs to support the Back/Forward cache

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 11 02:32:50 PDT 2008


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


cwzwarich at uwaterloo.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cwzwarich at uwaterloo.ca




------- Comment #3 from cwzwarich at uwaterloo.ca  2008-06-11 02:32 PDT -------
I turned the back/forward cache on in DumpRenderTree.mm, also adding

    [[webView backForwardList] init];

to resetWebViewToConsistentStateBeforeTesting() (otherwise you get over 1000
tests failing). Correct me if this is the wrong code to add. I had to turn off
http/tests/navigation, because dumpBackForwardListForWebView() expects the
previous test's back/forward items to be there as well, and asserts when they
aren't. I didn't really want to sit through 60 or so tests crashing.

Besides that, I only got 5 new failures:

fast/css/target-fragment-match.html
fast/dom/location-hash.htm
fast/forms/button-state-restore.html
fast/frames/frame-navigation.html       
fast/history/go-back-to-changed-name.html

When I run fast/js on its own, I get one test expecting a GC to occur that
doesn't. There are a few tests with new stderr output, and Apache had to be
killed during one HTTP test, which is fishy. 

I will try to work out the reasons for the failures. Hopefully we can turn the
back/forward cache on in DRT soon, and then we can write an interface to expose
it to tests. Is there any reason we want it to always be off for some existing
tests?


-- 
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