[re-post with better title - sorry for the dup but this is killing me!] If anyone from the GWT dev team is reading, please get in touch, we are struggling badly with this issue and would *really* appreciate any help.
We have a fairly big GWT app, and we are experiencing some issues when running it in IE. Sometimes (and there's no rhyme or reason to it) the app simply fails to start up. The HTML file is loaded by the browser, and the my.app.nocache.js file is loaded, but it then gets stuck. After a *lot* of debugging and cursing IE, we found out that it is stuck in the .nocache.js file waiting for the document readyState to become ready. There is a timer-function in this file, that goes off every 50ms, and checks to see if the $doc.readyState is "loaded" or "complete" and for some reason, when our app fails to load, the $doc.readyState never has either of those values (it seems to be stuck in "interactive"). When the app loads and runs correctly, this timer finds the readyState the first time it goes off, and it then triggers the app to be loaded. I see there is also an event-listener on the "DOMContentLoaded" event that effectively does the same thing, so it looks like the designers tried to work around this in more ways than one already. Obviously, in the cases where our app fails to start, this event is not firing either. Has anyone else ever seen this, or have any ideas about why IE is not setting the document readyState. I can see it might be because the document really isn't ready, but is there any way we can tell what it's waiting for? Any suggestions gratefully received Dave. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
