It works fine in hosted mode, and the crash happens only when the browser refresh button is clicked. I like the idea of inserting a few window.alerts to trace how far it makes it. I'll post here with progress, though it might be a bit since there are other issues that have precedence.
Thanks, Nevin On Sep 12, 6:02 pm, "Freeland Abbott" <[EMAIL PROTECTED]> wrote: > So loading works, but reloading the identical URL (same history token or > lack thereof, etc.) takes the browser down?! Wild. > Not that I can see why it should matter, but by "reload" are we talking > about something you do programmatically (e.g. META refresh, Window.open(), > etc.), pressing the loopy arrow button, or hitting return again in the > browser? > > The first thing I would check, though, is whether and how far things get on > the reload. For example, if you put a Window.alert early in onModuleLoad(), > is that reached? Can you watch what happens "on the wire" (or near > enough)... is the hosting page received, the *.nocache.js selector script, > the MD5-named compiled page? > > Also, does it misbehave in hosted mode? > > On Fri, Sep 12, 2008 at 7:03 PM, Nevin Freeman <[EMAIL PROTECTED]>wrote: > > > > > My app uses GWT, and the gwt-google-apis maps library. It loads > > perfectly fine in all browsers including Safari, but refreshing the > > app in Safari (3) reliably causes it to crash. I sent a report to > > Apple, figuring a browser crash is more their problem than GWT's, but > > I'd still like to try and make my app be reloadable in all browsers. > > Where do I even start with something like this? > > > Thanks, > > Nevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
