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 10137 - What criteria should browsers use to determine whether a URL's hash fragment differs from the previous one? Should the comparison be case-sensitive? Currently, all implementations of hashchange use case-sensitive comparisons except IE8, which uses a case-
Summary: What criteria should browsers use to determine whether a URL's hash fragment ...
Status: CLOSED 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: ---
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-07-12 18:49 UTC by contributor
Modified: 2010-10-04 14:46 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-12 18:49:48 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#history-traversal

Comment:
What criteria should browsers use to determine whether a URL's hash fragment
differs from the previous one? Should the comparison be case-sensitive?
Currently, all implementations of hashchange use case-sensitive comparisons
except IE8, which uses a case-insensitive comparison.

Posted from: 76.27.193.61
Comment 1 Ian 'Hixie' Hickson 2010-09-25 17:58:54 UTC 
Why would it be case-insensitive?

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: UAs differ so we need to clarify.
Comment 2 contributor 2010-09-25 17:59:15 UTC 
Checked in as WHATWG revision r5489.
Check-in comment: Only compare fragments for onhashchange, to make this work better with pushState(). Also, define it as case-sensitive.
http://html5.org/tools/web-apps-tracker?from=5488&to=5489
Comment 3 Ryan Grove 2010-09-25 19:38:00 UTC 
Perfect. Closing (I was the original commenter).