Comment #4 on issue 20341 by [email protected]: One layout test timeout from WebKit merge 47719:47732 http://code.google.com/p/chromium/issues/detail?id=20341
I've looked into this - it is failing because page cache is disabled(*) for chromium and thus we always try to reload the page on history->back() even if WebKitUsesPageCachePreferenceKey is set true. This causes infinite loop in the test as body's onload() is called each time we go away and come back. (*) More specifically, in chromium both FrameLoaderClientImpl::canCachePage() and ApplicationCacheHost::canCacheInPageCache() always return false (it's hard-coded). Should we mark this test WONTFIX and skip? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
