You may want to first look for "javascript:" in the generated JS (possibly in
PRETTY mode), to confirm Chromium engineer's findings.
--
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,
I tried switching our 2.7 code to use the direct injection linker, but still
saw the same issue. I will have another look at it tomorrow to see if I missed
something.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group
So apparently this has to do with javascript URLs, and indeed there have been
changes in 2.8.2. Apparently there are still some uses in the xsiframe linker
(should be javascript:'' though)
https://github.com/gwtproject/gwt/issues/8197#issuecomment-289413640
--
You received this message
We have 3 applications built with 2.7 & 2.8. None of them work, not sure what
version of GWT was used in the bits of AWS console that are broken. Looking at
the (possibly) offending change in Chromium, it appears to be concerned with
how JavaScript code is loaded in IFRAMES. This ties in with
FYI, Chromium issue 924105 has now been merged with
924317: https://bugs.chromium.org/p/chromium/issues/detail?id=924317
On Wednesday, January 23, 2019 at 12:50:01 PM UTC-5, Thomas Broyer wrote:
>
> The samples might very well use an old-ish version of GWT, I'm not sure
> they're updated each
On Tuesday, January 22, 2019 at 11:47:18 PM UTC+1, Jeff Ledgerwood wrote:
>
> GWT 2.8.0
>
>
> I am pulling my hair out with this error. Hoping someone can help. I am
> calling a Java method (in a GWT class) from an external javascript file.
> I've done this without issue with several other
The samples might very well use an old-ish version of GWT, I'm not sure
they're updated each time a release is cut (hard to tell, Showcase has been
built against an unreleased version, as shown by $gwt_version = "0.0.0" in
the *.cache.js).
On Wednesday, January 23, 2019 at 7:13:35 AM UTC+1,
It looks like a problem with how the GWT compiled javascript is being
injected into the page to me, I wonder if the GWT linker being used could
affect this? We specify the xsiframe linker which according to the docs is
the default. I can see the
