- From: <bugzilla@jessica.w3.org>
- Date: Mon, 20 Jun 2011 19:52:07 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12707
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-20 19:52:07 UTC ---
Ah, that wasn't clear. Will fix this too. (I guess the way to do it is to track
the current state and if the history is being navigated to that state, don't
fire popstate, or something. Would that handle #frag navs correctly?)
How should going back multiple steps in history, crossing a document boundary,
be handled?
e.g.:
...state3 | state4 | state5 ] [ state0 | state1 | state2...
where the first [..] is doc A and the second [..] is doc B, and the user
navigates from state1 in docB to state4 in docA in one traversal operation.
What popstates should fire, if any?
How about state5->state3 or state3->state5?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 20 June 2011 19:52:08 UTC