A little problem with the new URL hashes

[trevor]

I noticed the new changes made for the topic.tpl and the URL hashes.

When scrolling through each post in any particular topic the URL #NUM at the end changes - which is cool, love it.

Now when scrolling through on Chrome, not sure about any other browser, but on chrome the favicon flickers when scrolling either up or down. Additionally, while this nice to have, its also a tad bit CPU intensive on the client-side of things. Feels sluggish and unstable IMO.

Does anyone else have the same problem?

[kelso]

Im seeing the same behavior..

[frissdiegurke]

I don't see the favicon flickering (chrome too) but the 'reload' button always switches to 'stop' button (regardless if the title has changed on each scroll)
So maybe it's just a missing check whether the location needs to change?

[trevor]

@frissdiegurke said:

I don't see the favicon flickering (chrome too) but the 'reload' button always switches to 'stop' button (regardless if the title has changed on each scroll)
So maybe it's just a missing check whether the location needs to change?

The favicon and the reload flickers. @_@

[finid]

@trevor

On a Linux box: The Reload/Stop button flickers on Chromium, but not on Firefox.

[trevor]

I'll test it on Firefox and Safari.

[trevor]

Seems to be working fine in FF.

[baris]

history.replaceState doesn't seem to play well with all browsers/platforms. I see the favicon reload button flicker occasionally. http://keyes.ie/pushstate-and-replacestate-bug-in-chrome/ and progress on the bug on chrome https://code.google.com/p/chromium/issues/detail?id=50298

[julian]

We wanted to go a simpler route with this... I originally thought we could just alter window.location.hash, but as it turns out, if you do that, on Firefox, it goes to the hash, whereas on Chrome, it does nothing. So that ruled out simplicity...

[trevor]

Ah okay, thats more reasonable as it stands.
Thanks @baris @julian for the clarification!