Anyone have any idea on this ? It seems strange to me that the ISP could do this kind of "alteration" to the code. Although the tests I did so far seem to confirm this : I tested my apps on two other ISPs mobiles and it worked. (There are 3 majors mobile ISPs here in France, one of which - *SFR* is doing this).
Am-I the only one having this problem ? Many thanks ! Le dimanche 6 octobre 2013 12:20:26 UTC+2, Martones a écrit : > > Hi Jens, > > This is exactly the case. The nocache.js is gone and there is a bunch of > JS directly in the page. I first though that this is GWT behaviour but > couldnt explain it to myself. > > I guess it means that the pretty compiled code is too havy to be included > to the page. > Do you think there is anything to be done to be able to use obfuscation ? > (A dirty solution would be to place all the GWT files in the root folder > ... :p ). > > Many thanks ! > > > Le samedi 5 octobre 2013 23:16:56 UTC+2, Jens a écrit : >> >> Maybe your 3G provider optimizes web pages on the fly and inlines >> JavaScript automatically? How does the HTML source of your index page look >> like once the browser has loaded it (use FireBug / Chrome/Safari DevTools)? >> Does it still contain <script src='<module-name>/app.nocache.js'/> ? >> >> -- J. >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
