In addition, I am using GWT 1.4.62. I momentarily upgraded to the 1.5 RC2 , but I did not see any improvements.
On Aug 27, 11:16 am, bwarner <[EMAIL PROTECTED]> wrote: > I am noticing some strange behavior in IE7 with the HistoryListener. > It seems that when I click on a hyperlink in my application using IE, > there is always a 2-3 second delay before the onHistoryChanged method > is actually called. I have tested this with Window.alerts() in the > beginning of the onHistoryChanged method, and it is consistent across > all my pages. > > When I test my application in Mozilla (2.1 & 3.0), there is no lag, > and the onHistoryChanged method is immediately called (making a very > more responsive application). > > I have been developing an application with GWT for the past 5 months, > so the Javascript is quite large (~1.1 MB OBF). I have many modules > (30-40), and for now, I have them included all under one entry point. > I could break them out into 3 entry points, but I wanted to get some > feedback on what might be the possible problem. Is having one entry > point (and thus a large JS file) the culprit in IE? Or is it just a > browser problem? From what I understand, events bubble up in IE, and > thus there could be a delay before the onHistoryChanged handles the > event. > > Has anyone else noticed similar behavior? It just seems annoying > because it makes the application seem very unresponsive in IE. > Whatever feedback would be appreciated. > > Thanks > Bryan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
