Bug 110484 – Pages served out of the Page Cache/FBCache are different from the state they were before being cached

• Component: History
• Status: UNCONFIRMED

[Luca Grulla]

Webkit is only partially reproduce the last status of a page once served via the page cache.

In particular everything that has been dynamically added via javascript is discarded.

See the attached test.html file:

1) click the "add" button to dynamically add nodes to the DOM
2) click "click for WebKit" to navigate to www.webkit.org
3) click the browser back button
4) the page is reloaded from the FBCache but the node previously added to the DOM via javascript are not there

I would expect the nodes added via javascript to be there.

Tested on:
Chrome  25.0.1364.84 beta
Safari 6.0.2 (8536.26.17)


regards,
Luca Grulla

[Luca Grulla]

Created attachment 189544 [details]
test file replicating the bug

[Alexey Proskuryakov]

I cannot reproduce this in Safari.

This is expected in Chromium, because it does not use back/forward cache at all.

[Luca Grulla]

Hi Alexey thank you for your comment.

I have to confirm that I cannot reproduce myself the bug  with Safari anymore: apologise for the confusion and the wasted time.

Regarding Chromium: it does preserve that status of standard HTML field. If I type something in the input text on the top right of the example code I attached, then click on the webkit link and then hit the back button the content of the text field is there.  Shouldn't the input field be empty in order to not keeping any state then?

[Alexey Proskuryakov]

Restoring form content on uncached back/forward navigations is a separate feature that WebKit has, so this is expected.

I'm not sure if it's worth tracking this as a separate bug, there are probably bugs about adding support for b/f cache in Chrome already. CC'ing some chromium folks.