Bug 8355 - window object's prototype does not persist in back/forward cache
Summary: window object's prototype does not persist in back/forward cache
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-12 21:56 PDT by Geoffrey Garen
Modified: 2009-04-26 14:46 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Geoffrey Garen 2006-04-12 21:56:53 PDT 
window.__proto__.x = 1;

navigate to another page

hit 'back'

window.__proto__.x = undefined!

Frame.cpp saveWindowProperties and restoreWindowProperties need to save and restore not only the property map but also the prototype chain. One simple way would be to add a __proto__ member to the property map before saving it.
Comment 1 Cameron Zwarich (cpst) 2008-06-11 00:48:53 PDT 
This is fixed now that we store the entire global object in the back/forward cache, but I can't make a layout test because of bug 13672. Perhaps we should close this and make a bug to make a test for it when DumpRenderTree supports the back/forward cache?