It looks like there's enough pushback on this that we may want to drop it for now and have someone look into why at least one internal app is having bizarre refresh problems. Mothballing this patch for now.
On Thu, Sep 3, 2009 at 11:24 AM, John Tamplin <[email protected]> wrote: > On Thu, Sep 3, 2009 at 11:12 AM, <[email protected]> wrote: > >> What conditions trigger this? >> >> Also, is it possible that somebody is relying on this. For example, what >> happens if you use a link to change the hash from outside a GWT app, >> assuming that the GWT app will catch it? >> > > I don't use IE except when testing, but I do have multiple bookmarks saved > within the same GWT app. I don't know that I ever use the bookmark to move > between history states rather than just selecting it in the app, but I could > imagine if the app was really large and complicated that I might. > > -- > John A. Tamplin > Software Engineer (GWT), Google > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
