Friday, January 25, 2019

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


As noted above, I got a 2.7.0 app working on Canary by editting the generated file [@name-to]/[@name-to].nocache.js, changing $='javascript:""' to $='about:blank'. That worked for all 3 of my 2.7.0 apps.

Also, I'll confirm that 2.8.2 fixed the problem in my flagship app for me. The only changes I made to my build.gradle file were to change Java source/targetCompatibility from 1.6 to 1.8, and change the gwtVersion from 2.7.0 to 2.8.2.

On Friday, January 25, 2019 at 9:30:03 AM UTC-5, Rodolfo M. Raya wrote:
I have an app that uses GWT 2.7.0 and fails in Canary. I can't upgrade to GWT 2.8.2 because the app uses an old version of GXT.

What can I do to make my app work on Canary?


On Tue, Jan 22, 2019 at 9:40 AM Rob <> wrote:
We've just tried to use our GWT app with Chrome Canary only to find that it is terminally broken. The GWT showcase app ( exhibits the same behaviour and we've also seen it on certain AWS console pages. It appears to be event related, so hopefully the Chrome devs will fix it.

Has anyone else noticed this?

-- ...

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