Bug 56249 (hash-replacestate) - When a hash is set via location.hash then replaced via history.replaceState, history.back fails to go to the correct state
Summary: When a hash is set via location.hash then replaced via history.replaceState, ...
Status: RESOLVED FIXED
Alias: hash-replacestate
Product: WebKit
Classification: Unclassified
Component: History (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Nobody
URL: https://gist.github.com/867260
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-12 06:21 PST by Benjamin Lupton
Modified: 2011-03-14 11:03 PDT (History)
3 users (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 Benjamin Lupton 2011-03-12 06:21:33 PST 
A reproducible demo file is here:
https://gist.github.com/867260

A screenflow of the problem is here:
http://www.youtube.com/watch?v=zO4z-gMYhp0

This bug is only in Safari 5, and not in Google Chrome.
Comment 1 Mihai Parparita 2011-03-14 10:43:40 PDT 
Can you check this in nightly builds from http://nightly.webkit.org/? There have been quite a fix history changes between Safari 5 and the current Chrome stable channel build.
Comment 2 Benjamin Lupton 2011-03-14 11:01:24 PDT 
Correct Mihai, it's working fine (as expected) in the nightly: Version 5.0.4 (6533.20.27, r80833)

I'll be sure to check the nightlies next time before filing new bug reports :) Thanks!