So You re-add the script tags? Am Montag, 21. November 2016 12:27:33 UTC+1 schrieb Bruno Salmon: > > I found the problem, so I'm sharing the result of my investigation as this > may help other people facing a similar issue with Chrome 54+ or other > webkit based browsers: > > My app replaces the document <body> (which initially contains a splash > screen) with the application root element once loaded and initialized. This > replacement removed all previous elements under the <body> tag which were > actually not only the splash screen but also the <scripts> tags (this was > considered a best practice to put them here - not sure if this is still the > case with http2). > > Anyway removing the scripts tags once the application was loaded in memory > didn't cause any problem up to Chrome 54 and the application could continue > working as the scripts were already resident in memory. > > But from Chrome 54 this is not the case anymore: it seems removing the > script elements now immediately removes the resident application from the > memory as well. > > This is what caused my app stop working and even my timers programmed in > the initialization step were finally not called after the scripts tags have > been removed... > > > On Thursday, 27 October 2016 13:17:35 UTC+2, Bruno Salmon wrote: >> >> hi, >> >> My Chrome updated yesterday from version 53 to 54 and this made my GWT >> 2.8 app stop working. >> >> There is no error message in the console but after some investigation, I >> noticed that the problem come from the timers which are not called anymore >> (whatever the method: GWT Timer / Elemental2 / JSNI). It's like >> setTimeout() doesn't work anymore in the browser (and this is what freezes >> my app). >> >> However if I write a simple GWT 2.8 app whose code is just a timer >> invocation, it works in Chrome 54... >> >> The timers stop working only when I invoke my application logic (a quite >> big app). So it looks like something breaks the timers in the compiled >> javascript code, but I don't know how to investigate further (as the whole >> application logic run without error). >> >> My app works fine in FireFox. >> >> Any idea what's happening? >> >>
-- You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
