Bug 83369 - Window location is not updated correctly in Chrome Frame when '#' is present in the URL
Summary: Window location is not updated correctly in Chrome Frame when '#' is present ...
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: History (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Normal
Assignee: Nobody
URL: http://quirksmode.org/frametest.html
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-06 07:52 PDT by Yuriy Brayko
Modified: 2021-03-31 09:05 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuriy Brayko 2012-04-06 07:52:06 PDT 
Steps to reproduce:

1. Open any page in Chrome Frame under IE9 e.g. http://quirksmode.org/frametest.html
2. Add #123 to URL (http://quirksmode.org/frametest.html#123) and press Enter. 
3. Note that the first time window.location will be updated correctly:
...
hash: "#123"
href: "http://quirksmode.org/frametest.html#123"
...

4. Now change the hash e.g. to #1234 (http://quirksmode.org/frametest.html#1234) and press Enter
5. Window location object is not updated.

Result: 
window.location.hash is still "123" and window.location.href is "http://quirksmode.org/frametest.html#123"

Expected:
window.location.hash should be "1234" and window.location.href should be "http://quirksmode.org/frametest.html#1234"

Window location object will be updated only first time when user changes hash part of URL or pastes links with hashes to the same page more than once.