Well, this problem might be the 1016 Chromium issue http://code.google.com/p/chromium/issues/detail?id=1016
My situation is not exactly the same, because the 1016 issue appears to only affect history that should be there for hash changes. My issue is that the history state for the website prior to making the first hash change is lost. I can think of no way to test a browser with JS to detect whether it will behave this way. I can only think that I should detect the browser being used and process accordingly. Thankfully doing that can and will solve my particular problem with this behavior (you would need to understand what my app is doing to know why) but it is not a general solution to the problem. It is also very much a "hack" solution because as soon as chrome is patched to fix this issue I will have to modify my app to not act specially for chrome. If anyone has any further insight to help me or questions please let me know. Thanks On Oct 13, 1:21 pm, Sky <myonceinalifet...@gmail.com> wrote: > GWT's History object, which allows you to create browser history > within a GWT ajax app, works differently across browsers. > > Within IE, FF and Safari calling History.newItem(String historyToken, > boolean issueEvent) for the first time adds a browser history state on > top of the history event of navigating to the GWT web app. > > ie. Start at sitehttp://google.comthen navigate tohttp://myapp.appspot.com > (made up site) then interact with the site to go > tohttp://myapp.appspot.com#page2 > and your history will look like: > > myapp - page2 > myapp - home > Google > > Within Opera and Chrome (normal channel as well as dev channel) > calling History.newItem() for the first time replaces the history > state of navigating to the GWT web app. > > The above example results in the following history: > > myapp page2 > Google > > While this may be a bug, I don't care because I just need a way to > detect (with javascript or GWT) which way the browser will behave. > Does anyone know how I could detect this? The only thing I can think > of is to detect which browser the user is using in order to process > this situation. This obviously would be terrible programming because > if any of the browsers change their behavior I would need to change my > app. > > Many many thanks! > > p.s. the url to myapp.appspot.com is made up, I have no idea if it is > real. It was just for example. > > If you really need to see an example I could make an example site. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
