search

thanhlong203 / closure-library

Automatically exported from code.google.com/p/closure-library
0 stars 0 forks source link

function replaceToken in goog.History seems not work in chrome #344

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
List my environment first:
Linux Ubuntu 2.6.32
Chrome: 6.0.472

Test Case:
go to: 
http://closure-library.googlecode.com/svn/trunk/closure/goog/demos/history1.html
1. input aa to the input box, press "Set Token"
2. input bb to the input box, press "Set Token"
3. input cc to the input box, press "Replace Current Token"
4. input dd to the input box, press "Set Token"
Expected result: press backward button of the browser 3 times, the hash part of 
location should be "cc", "aa", "" respectively, and press forward button of the 
browser 3 times, the hash part of the location should be "aa", "cc", "dd" 
respectively. But on Chrome, it is total a mess.

I also have investigated that the function window.location.replace does not 
work correctly on Chrome, have the developers of Closure realized that?

Original issue reported on code.google.com by copperyb...@gmail.com on 5 Jul 2011 at 9:58

GoogleCodeExporter commented 8 years ago 
please contact me with email: zhihongzhang@yunrang.com

Original comment by copperyb...@gmail.com on 5 Jul 2011 at 10:00

GoogleCodeExporter commented 8 years ago 
Have you tried the demo in the latest Chrome?
I don't thnk anyone cares about Chrome 6 when Chrome 12 stable and Chrome 14 
dev are out.

Original comment by pall...@google.com on 5 Jul 2011 at 8:11

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I tried the latest Chrome 12.0.742.112 on WindowsXP
The bug still exist.
The history falls into total mess if you click backward and forward several 
times after you complete the first four steps.

Original comment by copperyb...@gmail.com on 6 Jul 2011 at 2:50

GoogleCodeExporter commented 8 years ago 
The bug is caused by http://crbug.com/1919
I don't think Closure can do anything against it.

You may use goog.history.Html5History in the browsers where available. It 
proved to be more stable in Chrome.

Original comment by pall...@google.com on 6 Jul 2011 at 1:08

GoogleCodeExporter commented 8 years ago 
Issue 366 has been merged into this issue.

Original comment by pall...@google.com on 19 Sep 2011 at 8:16

GoogleCodeExporter commented 8 years ago 
History is getting creaky and should be sunsetted eventually as HTML5 becomes 
available.  Closing if working in Chrome at head.  Chris seems to say bug is 
fixed at head.

Original comment by nn...@google.com on 9 May 2012 at 10:33