8782 2010-01-19 06:44:05 +0000 reinvestigate what parts of session history should be sync and what parts should be async 2010-10-04 14:29:56 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WORKSFORME http://www.whatwg.org/specs/web-apps/current-work/#history-traversal P3 normal LC 1 contributor ian fishd ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31114 0 contributor 2010-01-19 06:44:05 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#history-traversal Comment: reinvestigate what parts of session history should be sync and what parts should be async Posted from: 98.248.33.53 31115 1 ian 2010-01-19 06:56:03 +0000 I have some tests for this here: http://www.hixie.ch/tests/adhoc/dom/level0/history/sync-vs-async/ ...but other tests would be great. Things to look at include: * how should script authors know what onhashchange fired for if there's no state in the event, if it's async, and if the user clicked "back" twice quickly? * how should history.back() inside onpopstate/onhashchange work? 31896 2 ian 2010-02-13 10:57:07 +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: Accepted Change Description: no spec change Rationale: Handled this earlier when responding to e-mail threads.