However the bug is still there on the Chrome Dev version: Version
73.0.3679.0 (Official Build) dev (64-bit)
(Testing on Mac 10.14.2)
On Monday, January 28, 2019 at 3:13:23 AM UTC-5, Rob wrote:
>
> Can confirm that as mentioned in
> https://bugs.chromium.org/p/chromium/issues/detail?id=923585
>
Can confirm that as mentioned in
https://bugs.chromium.org/p/chromium/issues/detail?id=923585
Chrome Canary 74.0.3685.0 no longer suffers from this issue.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop
Many thanks, Thad. I will try that change.
Regards,
Rodolfo
On Fri, Jan 25, 2019 at 12:40 PM Thad Humphries
wrote:
> Rodolfo:
>
> As noted above, I got a 2.7.0 app working on Canary by editting the
> generated file [@name-to]/[@name-to].nocache.js, changing
> $='javascript:""' to
Rodolfo:
As noted above, I got a 2.7.0 app working on Canary by editting the
generated file [@name-to]/[@name-to].nocache.js, changing $='javascript:""'
to $='about:blank'. That worked for all 3 of my 2.7.0 apps.
Also, I'll confirm that 2.8.2 fixed the problem in my flagship app for me.
The
I have an app that uses GWT 2.7.0 and fails in Canary. I can't upgrade to
GWT 2.8.2 because the app uses an old version of GXT.
What can I do to make my app work on Canary?
Thanks,
Rodolfo
On Tue, Jan 22, 2019 at 9:40 AM Rob wrote:
> We've just tried to use our GWT app with Chrome Canary only
Managed to get our app building with 2.8.2 and can confirm that this fixes
the issue.
On Thursday, 24 January 2019 18:34:48 UTC, Rob wrote:
>
> Good to hear that 2.8.2 fixes it. Gives me an excuse to try and get our
> main app upgraded, unfortunately it's quite a complex app with a lot of
>
Some minor preprocessing with a custom linker, then hand off to the
default Cross-Site-Iframe.
On Thursday, January 24, 2019 at 12:16:54 PM UTC-8, Thad Humphries wrote:
>
> Are you using a particular linker in your *.gwt.xml file?
> http://www.gwtproject.org/doc/latest/DevGuideLinkers.html
>
>
Are you using a particular linker in your *.gwt.xml
file? http://www.gwtproject.org/doc/latest/DevGuideLinkers.html
On Thursday, January 24, 2019 at 1:19:05 PM UTC-5, Jim Douglas wrote:
>
> I think I can confirm that simply rebuilding with GWT 2.8.2 should resolve
> this issue for anyone
Well, I guess that was with older versions of IE, probably not relevant anymore
On 24 Jan 2019, 11:21 +0100, Rob , wrote:
> We are serving via HTTPS. I don't see any mixed content errors or warnings
> when running with this fix on either Chrome, Firefox, IE11, Edge or Safari 12
>
> On Thursday,
FWIW, we confirmed this breaks our in-market products (using 2.8.1 and
2.7.0). The Chromium issue is tagged with ReleaseBlock-Stable which I'm
*presuming* means this is an issue they will address before promoting this
to a stable build?
On Tuesday, January 22, 2019 at 4:39:46 AM UTC-8, Rob
What should be done , if can not switch to 2.8.2 for some reason?
On Fri, Jan 25, 2019 at 12:04 AM Rob wrote:
> Good to hear that 2.8.2 fixes it. Gives me an excuse to try and get our
> main app upgraded, unfortunately it's quite a complex app with a lot of
> inherited libraries so switching to
Good to hear that 2.8.2 fixes it. Gives me an excuse to try and get our
main app upgraded, unfortunately it's quite a complex app with a lot of
inherited libraries so switching to 2.8.2 involves a fair bit more than
just changing a version number.
--
You received this message because you are
I think I can confirm that simply rebuilding with GWT 2.8.2 should resolve
this issue for anyone experiencing it. We cut over our build systems to GWT
2.8.2 in November 2017, but I just did a test build here with 2.8.1. With
that test, none of my GWT apps will load in Chrome Canary. Switching
Does rebuilding with 2.8.2 remove/change $='javascript:""'? Is there a
setting I'll need in my *gwt.xml file? Will I also need that setting in the
GWT modules I include in my app?
On Thursday, January 24, 2019 at 1:56:13 AM UTC-5, Thomas Broyer wrote:
>
> You may want to first look for
That worked for me: I have 3 apps built with GWT 2.7.0. If I edit the
generated file [@name-to]/[@name-to].nocache.js, changing $='javascript:""'
to $='about:blank', all 3 apps now work in Canary.
As for SSL, I am not seeing any mixed content message in Chrome. I'm
running Apache 2.4 with a
Our apps are built with 2.7 & 2.8.1. Looking at the page Thomas linked to
it sounds like the problem is fixed in 2.8.2 which also explains why 'esoco
GmbH's app (mentioned above) works.
On Thursday, 24 January 2019 09:30:01 UTC, Frank wrote:
>
> To be clear : this does not affect GWT apps
We are serving via HTTPS. I don't see any mixed content errors or warnings
when running with this fix on either Chrome, Firefox, IE11, Edge or Safari
12
On Thursday, 24 January 2019 09:27:47 UTC, David Nouls wrote:
>
>
> Watch out with about:blank, if your app is running on SSL you will get
>
To be clear : this does not affect GWT apps build with 2.8.2 ?
--
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
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
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
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
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
I am seeing breakage with the GWT Showcase:
http://samples.gwtproject.org/samples/Showcase/Showcase.html
It looks ok in:
Version 71.0.3578.98 (Official Build) (64-bit)
But fails in: Version 73.0.3680.0 (Official Build) canary (64-bit)
(Where "fail" is "clicking in the top level menu doesn't
The game I wrote with GWT 2.8.2 works fine: https://drift.team/
However, an old project I wrote with GWT 2.7 (I think?), button clicks
don't work: https://www.invitbox.com/
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from
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
This fails on the dev channel as well. I created this bug report
https://bugs.chromium.org/p/chromium/issues/detail?id=924317=2=canary%20onclick%20event%20does%20not%20fire=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified
On Tuesday, January 22, 2019 at
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
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
>>
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
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,
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
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,
37 matches
Mail list logo
