This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8782 - reinvestigate what parts of session history should be sync and what parts should be async
Summary: reinvestigate what parts of session history should be sync and what parts sho...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-19 06:44 UTC by contributor
Modified: 2010-10-04 14:29 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-01-19 06:44:05 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-01-19 06:56:03 UTC 
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?
Comment 2 Ian 'Hixie' Hickson 2010-02-13 10:57:07 UTC 
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.