Wednesday, January 23, 2019

Re: Chrome Canary 73.0.3680.0 breaks pretty much ALL GWT apps :(

It looks like a problem with how the GWT compiled javascript is being injected into the page to me, I wonder if the GWT linker being used could affect this? We specify the xsiframe linker which according to the docs is the default. I can see the <script> tag being injected into the IFRAME when using the browser dev tools, but shortly afterwards the <script> tag disappears and none of my application source is available - hence it looks like it isn't even loading the application.

I can't look at the other apps listed above as our corporate firewall blocks them so can't see how they are being loaded.

On Wednesday, 23 January 2019 06:13:35 UTC, Jim Douglas wrote:
I am seeing breakage with the GWT Showcase:

It looks ok in: 
Version 71.0.3578.98 (Official Build) (64-bit)
But fails in: Version 73.0.3680.0 (Official Build) canary (64-bit)

(Where "fail" is "clicking in the top level menu doesn't seem to do anything").

On Tuesday, January 22, 2019 at 9:37:19 PM UTC-8, Craig Mitchell wrote:
The game I wrote with GWT 2.8.2 works fine:
However, an old project I wrote with GWT 2.7 (I think?), button clicks don't work:

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
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment