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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 25 18:14:03 PDT 2010


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





--- Comment #12 from Mihai Parparita <mihaip at chromium.org>  2010-08-25 18:14:03 PST ---
Now that I think about it some more, per the spec, I'm not sure Firefox is right to be firing popstate when going from #state1 to #state2 either (in addition to when going back). In that case, #state2 (the new entry) is not the first entry in the document, and doesn't have a state object. Same thing for when going from the initial state to #state1.

However, this all may be moot if Hixie agrees that popstate should fire for all history traversals.

P.S. Thanks for getting Hixie to make this change http://html5.org/tools/web-apps-tracker?from=5345&to=5346

-- 
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