The apps I tested are using GWT 2.8.2 Am Dienstag, 22. Januar 2019 15:43:02 UTC+1 schrieb Rob: > > 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 [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.
