window.location.replace not working on chrome ( 34 )

[cagosta]

Hey,

I use Hasher and for about two weeks my back button does not work anymore one my application. I have investigated and found that window.location.replace causes history to be completely lost. After using location.replace, when using back button, the page completely reload.

On any page, if you do this:

// on https://github.com/#foo
window.location.hash = '#bar'  // uri https://github.com/#bar
window.history.back() // uri  https://github.com/#foo

But if you do this:

// on https://github.com/#foo
window.location.hash = '#bar'  // uri https://github.com/#yo
window.location.replace('#baz ') // uri https://github.com/#bar 
window.history.back() // uri  https://github.com/, the all page reload 

Am I wrong ? Can somebody reproduce the bug ?

I'm running Chrome 34.0.1847.116 on Ubuntu 13.04
Everything is fine on Safari and Firefox.

As a solution, I have replaced the window.location.replace by window.history.replaceState but it works for modern browsers only.

[millermedeiros]

location.replace doesn't save the previous hash on the history (it overwrites the previous URI), so multiple consequent location.replace calls will save only 1 state on the history (just the last one).

if you need to go back and forward you should use hasher.setHash instead of hasher.replaceHash

[millermedeiros]

ohhh.. now I see what you're talking about.. it's probably a chrome bug. this error does reproduce on the unit tests: http://millermedeiros.github.io/Hasher/test/unit.html

[cagosta]

yes, on my chrome tests do not pass and the page ( randomly ? ) reloads.
This should be a chrome bug.

[millermedeiros]

It was reported to chrome: https://code.google.com/p/chromium/issues/detail?id=330943

Let's keep this issue open (so other users know what is going on) and star the chrome bug so that it gets more attention. Thanks for reporting it.

[cagosta]

Yes, this issue was mainly created to inform you and hasher's users of this.

Thank you

[millermedeiros]

this should be fixed now: https://code.google.com/p/chromium/issues/detail?id=363724