Google Web Toolkit

Tuesday, January 22, 2019

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

We're using GWT 2.8, maybe newer GWT code isn't affected?

On Tuesday, 22 January 2019 14:03:21 UTC, esoco GmbH wrote:

It doesn't seem to be a general problem. I just tried this with a deployed GWT application and another locally in development mode and both work as expected with Chrome 73.0.3680.0 (64-Bit) on Windows. I can reproduce the problem with the showcase but maybe that's caused by the site not running with HTTPS? As new browser versions are more and more rejecting unencrypted sites that may affect such old pages.

Am Dienstag, 22. Januar 2019 13:39:46 UTC+1 schrieb Rob:
We've just tried to use our GWT app with Chrome Canary only to find that it is terminally broken. The GWT showcase app (http://samples.gwtproject.org/samples/Showcase/Showcase.html) 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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

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

The showcase works fine on Chrome & Chrome Beta. Just not Canary. Same for our app and AWS console.

I've been debugging the GWT boot strapping code and can see that it appears to be failing as for some reason Canary is clearing out the IFRAME that the GWT app gets injected into.

On Tuesday, 22 January 2019 14:03:21 UTC, esoco GmbH wrote:

It doesn't seem to be a general problem. I just tried this with a deployed GWT application and another locally in development mode and both work as expected with Chrome 73.0.3680.0 (64-Bit) on Windows. I can reproduce the problem with the showcase but maybe that's caused by the site not running with HTTPS? As new browser versions are more and more rejecting unencrypted sites that may affect such old pages.

Am Dienstag, 22. Januar 2019 13:39:46 UTC+1 schrieb Rob:
We've just tried to use our GWT app with Chrome Canary only to find that it is terminally broken. The GWT showcase app (http://samples.gwtproject.org/samples/Showcase/Showcase.html) 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?

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

It doesn't seem to be a general problem. I just tried this with a deployed GWT application and another locally in development mode and both work as expected with Chrome 73.0.3680.0 (64-Bit) on Windows. I can reproduce the problem with the showcase but maybe that's caused by the site not running with HTTPS? As new browser versions are more and more rejecting unencrypted sites that may affect such old pages.

Am Dienstag, 22. Januar 2019 13:39:46 UTC+1 schrieb Rob:

We've just tried to use our GWT app with Chrome Canary only to find that it is terminally broken. The GWT showcase app (http://samples.gwtproject.org/samples/Showcase/Showcase.html) 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?

Chrome Canary 73.0.3680.0 breaks pretty much ALL GWT apps :(

We've just tried to use our GWT app with Chrome Canary only to find that it is terminally broken. The GWT showcase app (http://samples.gwtproject.org/samples/Showcase/Showcase.html) 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?

Monday, January 21, 2019

Re: java.nio.file.AccessDeniedException thrown on GWT compile

Thanks Jens. Been working all day, and not a single exception raised. So, looks like that was the problem. Cheers!

Sunday, January 20, 2019

Re: java.nio.file.AccessDeniedException thrown on GWT compile

Search in IntelliJ preferences for "safe write" and try disabling it.

-- J.

Re: java.nio.file.AccessDeniedException thrown on GWT compile

Correction: The exception is thrown before the compile even occurs. It seems to be random when it actually happens (however, it will only happen if code has been changed).

Once the exception has occurred, a refresh of the browser will still trigger a compile of the new code, which seems to complete, but never shows up in the browser until a restart is done on the GWT web server.

Running Java 1.8.0_192.