[Webkit-unassigned] [Bug 94181] New: Incorrect history.state after navigation
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Aug 15 20:38:38 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=94181
Summary: Incorrect history.state after navigation
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
URL: https://zewt.org/~glenn/test-webkit-incorrect-history-
state.html
OS/Version: Unspecified
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: History
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: glenn at zewt.org
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.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list