Thursday, January 24, 2019

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

Watch out with about:blank, if your app is running on SSL you will get mixed content warnings on some browsers... not sure if that is still the case, but that is one of the reasons why gwt was using javascript:""

On 24 Jan 2019, 10:01 +0100, Rob <>, wrote:

On Thursday, 24 January 2019 06:56:13 UTC, Thomas Broyer wrote:
You may want to first look for "javascript:" in the generated JS (possibly in PRETTY mode), to confirm Chromium engineer's findings.

Thanks Thomas for this prompt :) I looked again at the ticket you mentioned and replaced all of the javascript:'' & javascript:"" with about:blank and our application now loads in canary.

Using direct injection definitely didn't fix the issue for me, but I can now add a post processing step to our build to fix this. I guess it should in theory be possible to produce our own custom linker to do this properly?

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