Comments on: Google Chrome History Issue

By: kogmedia

kogmedia — Sat, 22 Nov 2008 00:52:56 +0000

I hesitate to use even upgraded versions of Chrome, since my last experience using it (first version) left my computer compromised; have they fixed the security issues beyond all doubt?

By: RedesignYourBiz

RedesignYourBiz — Tue, 21 Oct 2008 13:51:21 +0000

i just used google chrome for a couple of days and found out that firefox is the best and have now uninstalled google chrome :)

By: nathanhammond

nathanhammond — Sat, 18 Oct 2008 14:58:43 +0000

UPDATE! Great news! The wonderful people up in Mountain View have reopened Issue 151 making this plea unnecessary. And one more thing, since I don't feel I was clear enough about this, I want to make sure everyone knows that when the bug was closed it was a misunderstanding, not Google/Chrome willfully trying to break the web. I really appreciate their attention to this issue.

By: nathanhammond

nathanhammond — Fri, 17 Oct 2008 17:29:05 +0000

@lnostdal
The concern I have most specifically is that in this one particular instance the bug has not been been acknowledged and closed as “wontfix.” That is why I’m differentiating between this bug and and the other myriad bugs in Chrome which will all (hopefully) be addressed in time.

By: lnostdal

lnostdal — Fri, 17 Oct 2008 16:49:20 +0000

oh, there are plenty of stupid bugs .. this one has been bothering me for quite some time:
http://code.google.com/p/chromium/issues/detail?id=1919

By: nathanhammond

nathanhammond — Thu, 16 Oct 2008 17:47:24 +0000

@Jordan1 From further testing it appears that user-entered input may work. I provided that scenario in my blog post primarily to demonstrate the functionality I'm looking for. That it at leaast supports the functionality to that degree gives me hope that it will be a simple fix. However, in my simple test case for JSSM you can note a difference between the results for Firefox and Chrome. (Testing procedure: navigate a few jages within the site, navigate away, return to site.) @zbuffered My understanding of the reason YUI works is because it stores the whole of the history state in the hash (as does ASP.NET Ajax). As each of the history states is correctly associated to a history point in Chrome the problems only lie with trying to store additional information that you do not wish to place in the location bar. That is a functionality that (to my knowledge) exists only in RSH right now, and closely imitates the HTML 5 History Spec's pushState(). In fact, it is a functionality we'll be relying upon to implement a HTML 5 History shim to enable old browsers to use the same interface as future browsers that do support it. In general, that it breaks any existing implementation is unacceptable as now there are sites on the web which do not function as intended. However, there is light at the end of the tunnel, maybe. The whole reason I wanted this to appear here was to get it the attention it needs.

By: zbuffered

zbuffered — Thu, 16 Oct 2008 15:14:38 +0000

My production history implementation with the YUI history framework works solidly in Chrome and all other browsers (including IE6 but excluding Opera).

By: Jordan1

Jordan1 — Thu, 16 Oct 2008 14:57:17 +0000

I can’t reproduce this bug. I type a comment here in the comment box. Press my homepage button. Then click the browser back button and my half typed comment is still here. Then I click back and then click forward and my comment is still here.