[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 #10 from Justin Lebar <justin.lebar+bug at gmail.com>  2010-08-25 14:17:21 PST ---
(In reply to comment #9)
> What about the case where we navigate to two different fragments, and then go back twice (see updated test case attachment)? Gecko fires popstate for both history.back() calls, but it seems like first time (when going back from #state2 to #state1), the specified entry is not the first in the document, and it doesn't have a state object, so the conditions in step 10 of 6.5.9 (http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html#history-traversal) don't apply.

Hm...yes, I think you're reading that correctly.  FWIW I think that rule is way too confusing.  We should fire popState whenever the history entry changes, period.  That's much easier for people to understand.  Some pages might have to filter out noisy popstates, but that's better than the alternative.

Could you write to the WhatWG list about this?

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