Manual test added in http://trac.webkit.org/changeset/70321 can be a layouttest Using: layoutTestController.overridePreference("WebKitUsesPageCachePreferenceKey", 1); DRT *does* support the page cache.
<rdar://problem/22550195>
Created attachment 260456 [details] Layout test
Comment on attachment 260456 [details] Layout test View in context: https://bugs.webkit.org/attachment.cgi?id=260456&action=review r=me > LayoutTests/compositing/show-composited-iframe-on-back-button.html:17 > + // First time the page has been loaded. > + testRunner.queueLoad("resources/composited-subframe.html"); > + testRunner.queueBackNavigation(1); > + testRunner.queueForwardNavigation(1); > + testRunner.queueBackNavigation(1); The test says that the bug occurs when navigating to a new page and coming back to this one. Why is it necessary to go forward and back a second time?
(In reply to comment #3) > Comment on attachment 260456 [details] > Layout test > > View in context: > https://bugs.webkit.org/attachment.cgi?id=260456&action=review > > r=me > > > LayoutTests/compositing/show-composited-iframe-on-back-button.html:17 > > + // First time the page has been loaded. > > + testRunner.queueLoad("resources/composited-subframe.html"); > > + testRunner.queueBackNavigation(1); > > + testRunner.queueForwardNavigation(1); > > + testRunner.queueBackNavigation(1); > > The test says that the bug occurs when navigating to a new page and coming > back to this one. Why is it necessary to go forward and back a second time? It is not necessary. Will fix before landing.
Committed r189490: <http://trac.webkit.org/changeset/189490>