This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Often a web application will change states as the user works with it. If the user were to do a "refresh" in the browser, the state is generally lost unless the underlying javascript and/or server do a lot of work to keep track of this. The simplest method for doing this would be to tell the browser that if a refresh is done, it should go to a specific url other than the original. Obviously this could have big security implications so it would be reasonable to restrict the url to the current domain or even the current page (use '#' or '?' to get the server and javascript to get the correct state back).
Consider : location.refreshUrl = '#page45'; This would affect the refresh so that when the browser effects a refresh, the refreshed url would be "http://www.somesite.com/ajaxPage.html#page45".
This is already possible with history.pushState() as far as I can tell.
Mass move to "HTML WG"
Started thread on public-html: http://lists.w3.org/Archives/Public/public-html/2013Feb/0000.html
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: Agreed with Maciej on the discussion at: http://lists.w3.org/Archives/Public/public-html/2013Feb/0022.html