Hmmm, Thats not good news, could you provide more information about the custom selection script/linkers?
Also, I was wondering, if we were to mimic, the .nocache.js file, by calling its internal methods, would this be a problem when we deploy to production code and obfuscate the javascript code? (i.e. as all the method names/variables change to smaller less significant names) On Mar 20, 2:18 am, Thomas Broyer <[email protected]> wrote: > On 19 mar, 11:23, markmac <[email protected]> wrote: > > > Hi Vitali, > > > That is actually what we just thought of doing after I posted the > > question! Thanks for the help, but so far its not working, actually it > > looks like its doing nothing... I will investigate and find out whats > > going on, and post back once I find out. > > AFAICT, it waits for the page to be loaded (DOMContentLoaded or > similar, or onload as a last resort); so if the page already *is* > loaded when the script executes, it won't load the app. > > You'd have to use a custom selection script (and therefore a custom > Linker) that doesn't wait for DOMContentLoaded/onload. Or if you could > come up with a patch to the existing selection script template that > would make it work in either situation, I guess the GWT team would > happily integrate it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
