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 12382 - The traverse the history by a delta algorithm breaks down if a history traversal is already queued.
Summary: The traverse the history by a delta algorithm breaks down if a history traver...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
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: 2011-03-26 23:34 UTC by contributor
Modified: 2011-08-04 05:02 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-03-26 23:34:38 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/history.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-history-interface

Comment:
The traverse the history by a delta algorithm breaks down if a history
traversal is already queued.

Posted from: 70.169.186.78
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.2a1pre) Gecko/20110326 Firefox/4.2a1pre
Comment 1 Kyle Huey 2011-03-26 23:37:52 UTC 
In particular, consider a script that executes

window.history.back();
window.history.back();

If I'm reading the spec correctly, currently two tasks would be queued to traverse a delta of -1.
Comment 2 Ian 'Hixie' Hickson 2011-06-15 04:35:49 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: Rejected
Change Description: no spec change
Rationale: 

Correct. This is what browsers do, as far as I can tell.
Comment 3 Michael[tm] Smith 2011-08-04 05:02:51 UTC 
mass-moved component to LC1