15366 2011-12-30 11:21:40 +0000 Expose history traversal direction 2013-02-12 22:41:22 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED WORKSFORME P2 enhancement --- 1 annevk eoconnor eoconnor ian mail mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 62146 0 annevk 2011-12-30 11:21:40 +0000 E.g. for CSS transitions it would be nice if history traversal direction was known. Especially now there's history.pushState(). You can track this yourself but it would be nicer if it was explicitly exposed. (Feedback from Ben Joffe.) 62158 1 mail 2011-12-30 11:35:00 +0000 Perhaps this could be a property of the event object as an integer (defined the same as the argument that could have been passed to history.go to trigger the navigation). Another reason to want this property: some navigational states may be associated with an xhr request, if the navigation is back then it may be appropriate to display the previous result of that request, but if it is forward it may be appropriate to redo the request. 63501 2 ian 2012-02-01 00:54:32 +0000 Interesting idea. Sometimes the direction is forward relative to the last state that was active in the document, but backward relative to the last active entry in the session history, what would you do for that? 70093 3 contributor 2012-07-18 06:53:28 +0000 This bug was cloned to create bug 17811 as part of operation convergence. 75165 4 eoconnor 2012-10-02 23:51:38 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No spec change. Rationale: Let's consider this for HTML.next. 81742 5 robin 2013-01-21 15:59:59 +0000 Mass move to "HTML WG" 81860 6 robin 2013-01-21 16:02:45 +0000 Mass move to "HTML WG" 83059 7 eoconnor 2013-02-12 22:41:22 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No spec change. Rationale: As far as I can tell, the platform already provides the relevant features. (N.B. the discussion on bug 17811.)