Bug 94181

Summary: Incorrect history.state after navigation
Product: WebKit Reporter: Glenn Maynard <glenn>
Component: HistoryAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Normal CC: beidson, jjjaquanrice
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://zewt.org/~glenn/test-webkit-incorrect-history-state.html
Attachments:
Description Flags
test none

Glenn Maynard
Reported 2012-08-15 20:39:11 PDT
Be sure to run this test from a fresh window. Since it's testing window.history, reloading the page may cause different behavior. 1. Click the "A" button. 2. Click the "B" button. 3. Press browser back. (The hash is now #A.) 4. Click the "A" button. "e.state: null history.state: Object" is output to the console. The correct value is null. We navigated to a fragment identifier, which results in a new history entry; it has no state object. history.state ends up with an incorrect value. Also, when onpopstate is dispatched, e.state and history.state should always be equal; nothing happens between http://www.whatwg.org/specs/web-apps/current-work/#history-traversal steps 11 and 14 that can cause them to be different.
Attachments
test (64 bytes, text/plain)
2012-08-16 16:21 PDT, Glenn Maynard 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Brady Eidson
Comment 1 2012-08-16 09:42:19 PDT
For the confused among us, the test was in the URL field: https://zewt.org/~glenn/test-webkit-incorrect-history-state.html
Brady Eidson
Comment 2 2012-08-16 09:42:48 PDT
Could you attach the test case locally here?
Glenn Maynard
Comment 3 2012-08-16 16:21:59 PDT
Created attachment 158934 [details] test
Note You need to log in before you can comment on or make changes to this bug.