This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.)
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.
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?
This bug was cloned to create bug 17811 as part of operation convergence.
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.
Mass move to "HTML WG"
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.)