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 9193 - "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_
Summary: "If hash changed is true, then, if the new URL has a fragment identifier, scr...
Status: RESOLVED FIXED
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-03-05 01:30 UTC by contributor
Modified: 2010-10-04 14:56 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-03-05 01:30:16 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-03-30 21:47:55 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: see diff given below
Rationale: Concurred with reporter's comments.
Comment 2 contributor 2010-03-30 21:48:41 UTC 
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