[Webkit-unassigned] [Bug 33538] New: push/replaceState() during load followed by a history.back() doesn't work as expected.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Jan 12 10:49:51 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=33538
Summary: push/replaceState() during load followed by a
history.back() doesn't work as expected.
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P2
Component: Page Loading
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: beidson at apple.com
Created an attachment (id=46382)
--> (https://bugs.webkit.org/attachment.cgi?id=46382)
Test case
push/replaceState() during load followed by a history.back() doesn't work as
expected.
According to 10.5.3 of the spec
(http://dev.w3.org/html5/spec/Overview.html#activating-state-object-entries),
if a state object is popped before the document has loaded, that popped state
object becomes the "pending" state object and the event is to-be-fired after
the load event fires.
I thought I had this working originally when working on the ajaxy history
stuff, but apparently missed it in the end.
See the attached test case.
The output is:
Pushing state - document.readyState is loading
Popping state - document.readyState is loading
State popped - null (type object) - document.readyState is complete
And I'd expect it to be:
Pushing state - document.readyState is loading
Popping state - document.readyState is loading
Load event fired - document.readyState is complete
State popped - New state (type string) - document.readyState is complete
--
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