9193 2010-03-05 01:30:16 +0000 "If hash changed is true, then, if the new URL has a fragment identifier, scroll to the fragment identifier." is wrong. It should scroll if it's a new entry that hasn't been traversed to before, even if it's the same fragid as before; and it should _not_ 2010-10-04 14:56:57 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#history-traversal P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 32818 0 contributor 2010-03-05 01:30:16 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#history-traversal Comment: "If hash changed is true, then, if the new URL has a fragment identifier, scroll to the fragment identifier." is wrong. It should scroll if it's a new entry that hasn't been traversed to before, even if it's the same fragid as before; and it should _not_ scroll to the fragid if just going back. Posted from: 216.239.45.4 by ian@hixie.ch 34167 1 ian 2010-03-30 21:47:55 +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: see diff given below Rationale: Concurred with reporter's comments. 34168 2 contributor 2010-03-30 21:48:41 +0000 Checked in as WHATWG revision r4904. Check-in comment: Make history traversal scroll to fragmend identifiers correctly. http://html5.org/tools/web-apps-tracker?from=4903&to=4904