What specific issues are people seeing? I just poked around in my company's GWT 2.8.2 sample apps in Chrome Canary (Version 73.0.3680.0 (Official Build) canary (64-bit)) under macOS Mojave 10.14.2:
https://www.google.com/chrome/canary/?platform=mac https://bbjserver.basis.com:8443/files/showcase/index.html I didn't do an exhaustive test, but I'm not seeing any obvious problems. On Tuesday, January 22, 2019 at 2:51:08 PM UTC-8, jlm wrote: > > This fails on the dev channel as well. I created this bug report > > https://bugs.chromium.org/p/chromium/issues/detail?id=924317&can=2&q=canary%20onclick%20event%20does%20not%20fire&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified > > > On Tuesday, January 22, 2019 at 10:42:47 AM UTC-5, Thad Humphries wrote: >> >> I am seeing similar problems with Canary and three production apps written >> and built with GWT 2.7.0. Two apps fail to load anything beyond the >> index.html's background image. The third app (which uses some MGWT) loads >> the initial UI, but does not respond to a button click. All apps behave fine >> in standard Chrome. >> >> OS: Mojave 10.14.2 >> Chrome standard: 71.0.3578.98 >> Chrome Canary: 73.0.3680.0 >> >> >> I also see the same problems with the GWT Showcase. >> >> >> My apps and GWT Showcase are also working in Safari 12.0.2 and Firefox >> 65.0b12 >> >> >> On Tuesday, January 22, 2019 at 9:40:51 AM UTC-5, Rob wrote: >>> >>> 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? >>>>> >>>> -- 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+unsubscr...@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.