Hm, if you have a consistently reproducible case of where the <script> tag does not load up properly in the body, I'd encourage you to file an issue at http://code.google.com/p/google-web-toolkit. That sounds like a bug in IE hosted mode.
On Tue, Jul 28, 2009 at 5:10 PM, Pavel Byles <[email protected]> wrote: > This might be a hosted mode specific thing, because it worked fine in FF. > Maybe when OOPHM in GWT is officially released then I can put it back in > the body. > > When I deploy it to AppEngine I put it back in the body and everything > works fine. > > On Mon, Jul 27, 2009 at 11:58 AM, Rajeev Dayal <[email protected]> wrote: > >> Actually, it is not necessary that the <script> tag be placed in the >> <head> section. You can place it in the <body> section. GWT's samples >> actually place the <script> reference in the <body>. Maybe you had placed it >> at a position in the body where the load was blocked waiting for your other >> script for evaluate? >> >> On Sat, Jul 25, 2009 at 11:14 AM, Pavel Byles <[email protected]>wrote: >> >>> I figured out the problem: >>> Just after I synced w/ my repo I had put the nocache.js script tag in my >>> body, which doesn't seem to load in hosted mode. But works just fine in >>> Firefox. Putting it back in the <head> makes it work again. >>> >>> >>> >>> >> >> >> > > > -- > -Pav > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
