[Webkit-unassigned] [Bug 41372] popstate event is not fired until document opts in by calling pushstate.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=41372





--- Comment #3 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2010-06-30 10:16:00 PST ---
> After a pushstate, only the second history entry has a state object, but Chrome 
> fires a popstate when you navigate to either the first or the second state 
> object.

When you pushstate, WebKit sets a null state object on the previous history entry.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.