Monday, January 28, 2019

Re: elemental2 indexeddb example?



On Monday, January 28, 2019 at 12:49:41 AM UTC+1, rhodebump wrote:
Thanks, I did make some progress.   I dug around a little in the javadoc and found the IndexedDbGlobal, which I was able to use to create a new database.


elemental2.indexeddb.IDBFactory indexedDB = elemental2.indexeddb.IndexedDbGlobal.indexedDB;

elemental2.indexeddb.IDBOpenDBRequest openDBRequest = indexedDB.open("mydbtest", 1.0);


So far so good.


With a open database call, I get a returned object of elemental2.indexeddb.IDBOpenDBRequest (https://static.javadoc.io/com.google.elemental2/elemental2-indexeddb/1.0.0-RC1/elemental2/indexeddb/IDBOpenDBRequest.html)



In the google documentation that I have found that describes the indexedDB open operation, https://developers.google.com/web/ilt/pwa/working-with-indexeddb#opening_a_database


They provide the following code:

  var dbPromise = idb.open('test-db2', 1, function(upgradeDb) {
    console
.log('making a new object store');
   
if (!upgradeDb.objectStoreNames.contains('firstOS')) {
      upgradeDb
.createObjectStore('firstOS');
   
}
 
});


Note that this is using the IndexedDB Promised library, not the IndexedDB API (see https://developers.google.com/web/ilt/pwa/working-with-indexeddb#comparison_of_indexeddb_api_and_indexeddb_promised_library)
Fwiw, I'd rather use https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API as a reference.
 
I want to register a function to execute when the database is upgraded.  I see there is a openDBRequest.onupgradeneeded(), but I just can't the syntax right.


elemental2.indexeddb.IDBFactory indexedDB = elemental2.indexeddb.IndexedDbGlobal.indexedDB;

elemental2.indexeddb.IDBOpenDBRequest openDBRequest = indexedDB.open("mydbtest", 1.0);


//how to i call a function for upgrade?  I want to create some object stores.

openDBRequest. onupgradeneeded = doUpgrade();

That would be something like:

openDBRequest.onupgradeneeded = new OnupgradeneededFn() {
 
@Override
 
public Object onInvoke(IDBVersionChangeEvent event) {
    doUpgrade
();
   
return Js.undefined(); // that value will likely be ignored anyway
 
}
};


or, using a lambda:

openDBRequest.onupgradeneeded = event -> {
  doUpgrade
();
 
return Js.undefined();
};

--
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+unsubscribe@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.

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

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

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 receiving emails from it, send an email to google-web-toolkit+unsubscribe@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.

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

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 receiving emails from it, send an email to google-web-toolkit+unsubscribe@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.

Sunday, January 27, 2019

Re: elemental2 indexeddb example?

Thanks, I did make some progress.   I dug around a little in the javadoc and found the IndexedDbGlobal, which I was able to use to create a new database.


elemental2.indexeddb.IDBFactory indexedDB = elemental2.indexeddb.IndexedDbGlobal.indexedDB;

elemental2.indexeddb.IDBOpenDBRequest openDBRequest = indexedDB.open("mydbtest", 1.0);


So far so good.


With a open database call, I get a returned object of elemental2.indexeddb.IDBOpenDBRequest (https://static.javadoc.io/com.google.elemental2/elemental2-indexeddb/1.0.0-RC1/elemental2/indexeddb/IDBOpenDBRequest.html)



In the google documentation that I have found that describes the indexedDB open operation, https://developers.google.com/web/ilt/pwa/working-with-indexeddb#opening_a_database


They provide the following code:

  var dbPromise = idb.open('test-db2', 1, function(upgradeDb) {
    console
.log('making a new object store');
   
if (!upgradeDb.objectStoreNames.contains('firstOS')) {
      upgradeDb
.createObjectStore('firstOS');
   
}
 
});

I want to register a function to execute when the database is upgraded.  I see there is a openDBRequest.onupgradeneeded(), but I just can't the syntax right.


elemental2.indexeddb.IDBFactory indexedDB = elemental2.indexeddb.IndexedDbGlobal.indexedDB;

elemental2.indexeddb.IDBOpenDBRequest openDBRequest = indexedDB.open("mydbtest", 1.0);


//how to i call a function for upgrade?  I want to create some object stores.

openDBRequest. onupgradeneeded = doUpgrade();

Thanks for your help.



On Sunday, January 27, 2019 at 5:48:37 AM UTC-5, Thomas Broyer wrote:
Elemental2 API map directly to the native browser APIs, so you'll start with IndexedDBGlobal.indexedDB and walk your way almost exactly like you'd do in JS.
Javadoc can be found here fwiw: https://javadoc.io/doc/com.google.elemental2/elemental2-indexeddb/1.0.0-RC1

On Sunday, January 27, 2019 at 5:57:44 AM UTC+1, rhodebump wrote:

I am interested in using indexeddb from within GWT.  I found the following library that indicates that it provides indexeddb support https://github.com/google/elemental2


Does anyone have an example of opening a database? 


Thanks,

Phillip



--
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+unsubscribe@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.

Re: elemental2 indexeddb example?

Elemental2 API map directly to the native browser APIs, so you'll start with IndexedDBGlobal.indexedDB and walk your way almost exactly like you'd do in JS.
Javadoc can be found here fwiw: https://javadoc.io/doc/com.google.elemental2/elemental2-indexeddb/1.0.0-RC1

On Sunday, January 27, 2019 at 5:57:44 AM UTC+1, rhodebump wrote:

I am interested in using indexeddb from within GWT.  I found the following library that indicates that it provides indexeddb support https://github.com/google/elemental2


Does anyone have an example of opening a database? 


Thanks,

Phillip



--
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+unsubscribe@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.

Saturday, January 26, 2019

elemental2 indexeddb example?


I am interested in using indexeddb from within GWT.  I found the following library that indicates that it provides indexeddb support https://github.com/google/elemental2


Does anyone have an example of opening a database? 


Thanks,

Phillip



--
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+unsubscribe@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.

Friday, January 25, 2019

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

Many thanks, Thad. I will try that change.

Regards,
Rodolfo 

On Fri, Jan 25, 2019 at 12:40 PM Thad Humphries <thad.humphries@gmail.com> 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 $='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 only changes I made to my build.gradle file were to change Java source/targetCompatibility from 1.6 to 1.8, and change the gwtVersion from 2.7.0 to 2.8.2.

On Friday, January 25, 2019 at 9:30:03 AM UTC-5, Rodolfo M. Raya wrote:
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 <rob.a...@gmail.com> wrote:
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+unsubscribe@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.


--

--
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+unsubscribe@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.

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

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 only changes I made to my build.gradle file were to change Java source/targetCompatibility from 1.6 to 1.8, and change the gwtVersion from 2.7.0 to 2.8.2.

On Friday, January 25, 2019 at 9:30:03 AM UTC-5, Rodolfo M. Raya wrote:
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 <rob.a...@gmail.com> wrote:
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+unsubscribe@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.

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

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 <rob.a.stone@gmail.com> wrote:
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+unsubscribe@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.


--

--
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+unsubscribe@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.

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

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 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 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+unsubscribe@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.

Thursday, January 24, 2019

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

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

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 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 back to GWT 2.8.2 immediately resolved the issue, with no other changes.

Compiled with GWT 2.8.1:

scrappy:gwtwebclient jimdouglas$ grep javascript *nocache*

function gwtwebclient(){var O='bootstrap',P='begin',Q='gwt.codesvr.gwtwebclient=',R='gwt.codesvr=',S='gwtwebclient',T='startup',U='DUMMY',V=0,W=1,X='iframe',Y='javascript:""',Z='position:absolute; width:0; height:0; border:none; left: -1000px;',$=' top: -1000px;',_='CSS1Compat',ab='<!doctype html>',bb='',cb='<html><head><\/head><body><\/body><\/html>',db='undefined',eb='readystatechange',fb=10,gb='Chrome',hb='eval("',ib='");',jb='script',kb='javascript',lb='moduleStartup',mb='moduleRequested',nb='Failed to load ',ob='head',pb='meta',qb='name',rb='gwtwebclient::',sb='::',tb='gwt:property',ub='content',vb='=',wb='gwt:onPropertyErrorFn',xb='Bad handler "',yb='" for "gwt:onPropertyErrorFn"',zb='gwt:onLoadErrorFn',Ab='" for "gwt:onLoadErrorFn"',Bb='#',Cb='?',Db='/',Eb='img',Fb='clear.cache.gif',Gb='baseUrl',Hb='gwtwebclient.nocache.js',Ib='base',Jb='//',Kb='user.agent',Lb='webkit',Mb='safari',Nb='msie',Ob=11,Pb='ie10',Qb=9,Rb='ie9',Sb=8,Tb='ie8',Ub='gecko',Vb='gecko1_8',Wb=2,Xb=3,Yb=4,Zb='selectingPermutation',$b='gwtwebclient.devmode.js',_b='1B074381A5A6D99AB6896BA4A3EF41CB',ac='2D63FF17625503B67A9A19DAAA6300D3',bc='5A6D94200904CC3FE501C45A9F1598A8',cc='75A52E0A57236FE95CC057202E391636',dc='E8A2397ED64648DD5BA91A420DB9A517',ec=':',fc='.cache.js',gc='loadExternalRefs',hc='end',ic='http:',jc='file:',kc='_gwt_dummy_',lc='__gwtDevModeHook:gwtwebclient',mc='Ignoring non-whitelisted Dev Mode URL: ',nc=':moduleBase';var o=window;var p=document;r(O,P);function q(){var a=o.location.search;return a.indexOf(Q)!=-1||a.indexOf(R)!=-1}


Compiled with GWT 2.8.2:


scrappy:gwtwebclient jimdouglas$ grep javascript *nocache*

function gwtwebclient(){var O='bootstrap',P='begin',Q='gwt.codesvr.gwtwebclient=',R='gwt.codesvr=',S='gwtwebclient',T='startup',U='DUMMY',V=0,W=1,X='iframe',Y='position:absolute; width:0; height:0; border:none; left: -1000px;',Z=' top: -1000px;',$='CSS1Compat',_='<!doctype html>',ab='',bb='<html><head><\/head><body><\/body><\/html>',cb='undefined',db='readystatechange',eb=10,fb='Chrome',gb='eval("',hb='");',ib='script',jb='javascript',kb='moduleStartup',lb='moduleRequested',mb='Failed to load ',nb='head',ob='meta',pb='name',qb='gwtwebclient::',rb='::',sb='gwt:property',tb='content',ub='=',vb='gwt:onPropertyErrorFn',wb='Bad handler "',xb='" for "gwt:onPropertyErrorFn"',yb='gwt:onLoadErrorFn',zb='" for "gwt:onLoadErrorFn"',Ab='#',Bb='?',Cb='/',Db='img',Eb='clear.cache.gif',Fb='baseUrl',Gb='gwtwebclient.nocache.js',Hb='base',Ib='//',Jb='user.agent',Kb='webkit',Lb='safari',Mb='msie',Nb=11,Ob='ie10',Pb=9,Qb='ie9',Rb=8,Sb='ie8',Tb='gecko',Ub='gecko1_8',Vb=2,Wb=3,Xb=4,Yb='selectingPermutation',Zb='gwtwebclient.devmode.js',$b='6143757447205109409E8E4B4B5953F5',_b='616DB373F0C08A308FAA7595CF1774F9',ac='84B5B6FF71219E39FBCAF33FD2B04BCF',bc='9EA5B1320930CAEB74A5FBB6B36A38B0',cc='CDA7348DD6F4462F42A88973CEE8B181',dc=':',ec='.cache.js',fc='loadExternalRefs',gc='end',hc='http:',ic='file:',jc='_gwt_dummy_',kc='__gwtDevModeHook:gwtwebclient',lc='Ignoring non-whitelisted Dev Mode URL: ',mc=':moduleBase';var o=window;var p=document;r(O,P);function q(){var a=o.location.search;return a.indexOf(Q)!=-1||a.indexOf(R)!=-1}

scrappy:gwtwebclient jimdouglas$ 


Is there a button someone can push to rebuild http://samples.gwtproject.org/samples/Showcase/Showcase.html with GWT 2.8.2 to see if that fixes the GWT showcase?


On Thursday, January 24, 2019 at 7:11:56 AM UTC-8, Thad Humphries wrote:
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 "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, send an email to google-web-toolkit+unsubscribe@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.

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

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 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 back to GWT 2.8.2 immediately resolved the issue, with no other changes.

Compiled with GWT 2.8.1:

scrappy:gwtwebclient jimdouglas$ grep javascript *nocache*

function gwtwebclient(){var O='bootstrap',P='begin',Q='gwt.codesvr.gwtwebclient=',R='gwt.codesvr=',S='gwtwebclient',T='startup',U='DUMMY',V=0,W=1,X='iframe',Y='javascript:""',Z='position:absolute; width:0; height:0; border:none; left: -1000px;',$=' top: -1000px;',_='CSS1Compat',ab='<!doctype html>',bb='',cb='<html><head><\/head><body><\/body><\/html>',db='undefined',eb='readystatechange',fb=10,gb='Chrome',hb='eval("',ib='");',jb='script',kb='javascript',lb='moduleStartup',mb='moduleRequested',nb='Failed to load ',ob='head',pb='meta',qb='name',rb='gwtwebclient::',sb='::',tb='gwt:property',ub='content',vb='=',wb='gwt:onPropertyErrorFn',xb='Bad handler "',yb='" for "gwt:onPropertyErrorFn"',zb='gwt:onLoadErrorFn',Ab='" for "gwt:onLoadErrorFn"',Bb='#',Cb='?',Db='/',Eb='img',Fb='clear.cache.gif',Gb='baseUrl',Hb='gwtwebclient.nocache.js',Ib='base',Jb='//',Kb='user.agent',Lb='webkit',Mb='safari',Nb='msie',Ob=11,Pb='ie10',Qb=9,Rb='ie9',Sb=8,Tb='ie8',Ub='gecko',Vb='gecko1_8',Wb=2,Xb=3,Yb=4,Zb='selectingPermutation',$b='gwtwebclient.devmode.js',_b='1B074381A5A6D99AB6896BA4A3EF41CB',ac='2D63FF17625503B67A9A19DAAA6300D3',bc='5A6D94200904CC3FE501C45A9F1598A8',cc='75A52E0A57236FE95CC057202E391636',dc='E8A2397ED64648DD5BA91A420DB9A517',ec=':',fc='.cache.js',gc='loadExternalRefs',hc='end',ic='http:',jc='file:',kc='_gwt_dummy_',lc='__gwtDevModeHook:gwtwebclient',mc='Ignoring non-whitelisted Dev Mode URL: ',nc=':moduleBase';var o=window;var p=document;r(O,P);function q(){var a=o.location.search;return a.indexOf(Q)!=-1||a.indexOf(R)!=-1}


Compiled with GWT 2.8.2:


scrappy:gwtwebclient jimdouglas$ grep javascript *nocache*

function gwtwebclient(){var O='bootstrap',P='begin',Q='gwt.codesvr.gwtwebclient=',R='gwt.codesvr=',S='gwtwebclient',T='startup',U='DUMMY',V=0,W=1,X='iframe',Y='position:absolute; width:0; height:0; border:none; left: -1000px;',Z=' top: -1000px;',$='CSS1Compat',_='<!doctype html>',ab='',bb='<html><head><\/head><body><\/body><\/html>',cb='undefined',db='readystatechange',eb=10,fb='Chrome',gb='eval("',hb='");',ib='script',jb='javascript',kb='moduleStartup',lb='moduleRequested',mb='Failed to load ',nb='head',ob='meta',pb='name',qb='gwtwebclient::',rb='::',sb='gwt:property',tb='content',ub='=',vb='gwt:onPropertyErrorFn',wb='Bad handler "',xb='" for "gwt:onPropertyErrorFn"',yb='gwt:onLoadErrorFn',zb='" for "gwt:onLoadErrorFn"',Ab='#',Bb='?',Cb='/',Db='img',Eb='clear.cache.gif',Fb='baseUrl',Gb='gwtwebclient.nocache.js',Hb='base',Ib='//',Jb='user.agent',Kb='webkit',Lb='safari',Mb='msie',Nb=11,Ob='ie10',Pb=9,Qb='ie9',Rb=8,Sb='ie8',Tb='gecko',Ub='gecko1_8',Vb=2,Wb=3,Xb=4,Yb='selectingPermutation',Zb='gwtwebclient.devmode.js',$b='6143757447205109409E8E4B4B5953F5',_b='616DB373F0C08A308FAA7595CF1774F9',ac='84B5B6FF71219E39FBCAF33FD2B04BCF',bc='9EA5B1320930CAEB74A5FBB6B36A38B0',cc='CDA7348DD6F4462F42A88973CEE8B181',dc=':',ec='.cache.js',fc='loadExternalRefs',gc='end',hc='http:',ic='file:',jc='_gwt_dummy_',kc='__gwtDevModeHook:gwtwebclient',lc='Ignoring non-whitelisted Dev Mode URL: ',mc=':moduleBase';var o=window;var p=document;r(O,P);function q(){var a=o.location.search;return a.indexOf(Q)!=-1||a.indexOf(R)!=-1}

scrappy:gwtwebclient jimdouglas$ 


Is there a button someone can push to rebuild http://samples.gwtproject.org/samples/Showcase/Showcase.html with GWT 2.8.2 to see if that fixes the GWT showcase?


On Thursday, January 24, 2019 at 7:11:56 AM UTC-8, Thad Humphries wrote:
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 "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, send an email to google-web-toolkit+unsubscribe@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.

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

Well, I guess that was with older versions of IE, probably not relevant anymore
On 24 Jan 2019, 11:21 +0100, Rob <rob.a.stone@gmail.com>, 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, 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 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:""

--
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+unsubscribe@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.

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

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 <rob.a.stone@gmail.com> 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 2.8.2 involves a fair bit more than just changing a version number. 

--
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+unsubscribe@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.


--
Nagin Kothari
Co-founder,
Zilicus Solutions
www.zilicus.com

--
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+unsubscribe@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.

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

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 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+unsubscribe@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.

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

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 back to GWT 2.8.2 immediately resolved the issue, with no other changes.

Compiled with GWT 2.8.1:

scrappy:gwtwebclient jimdouglas$ grep javascript *nocache*

function gwtwebclient(){var O='bootstrap',P='begin',Q='gwt.codesvr.gwtwebclient=',R='gwt.codesvr=',S='gwtwebclient',T='startup',U='DUMMY',V=0,W=1,X='iframe',Y='javascript:""',Z='position:absolute; width:0; height:0; border:none; left: -1000px;',$=' top: -1000px;',_='CSS1Compat',ab='<!doctype html>',bb='',cb='<html><head><\/head><body><\/body><\/html>',db='undefined',eb='readystatechange',fb=10,gb='Chrome',hb='eval("',ib='");',jb='script',kb='javascript',lb='moduleStartup',mb='moduleRequested',nb='Failed to load ',ob='head',pb='meta',qb='name',rb='gwtwebclient::',sb='::',tb='gwt:property',ub='content',vb='=',wb='gwt:onPropertyErrorFn',xb='Bad handler "',yb='" for "gwt:onPropertyErrorFn"',zb='gwt:onLoadErrorFn',Ab='" for "gwt:onLoadErrorFn"',Bb='#',Cb='?',Db='/',Eb='img',Fb='clear.cache.gif',Gb='baseUrl',Hb='gwtwebclient.nocache.js',Ib='base',Jb='//',Kb='user.agent',Lb='webkit',Mb='safari',Nb='msie',Ob=11,Pb='ie10',Qb=9,Rb='ie9',Sb=8,Tb='ie8',Ub='gecko',Vb='gecko1_8',Wb=2,Xb=3,Yb=4,Zb='selectingPermutation',$b='gwtwebclient.devmode.js',_b='1B074381A5A6D99AB6896BA4A3EF41CB',ac='2D63FF17625503B67A9A19DAAA6300D3',bc='5A6D94200904CC3FE501C45A9F1598A8',cc='75A52E0A57236FE95CC057202E391636',dc='E8A2397ED64648DD5BA91A420DB9A517',ec=':',fc='.cache.js',gc='loadExternalRefs',hc='end',ic='http:',jc='file:',kc='_gwt_dummy_',lc='__gwtDevModeHook:gwtwebclient',mc='Ignoring non-whitelisted Dev Mode URL: ',nc=':moduleBase';var o=window;var p=document;r(O,P);function q(){var a=o.location.search;return a.indexOf(Q)!=-1||a.indexOf(R)!=-1}


Compiled with GWT 2.8.2:


scrappy:gwtwebclient jimdouglas$ grep javascript *nocache*

function gwtwebclient(){var O='bootstrap',P='begin',Q='gwt.codesvr.gwtwebclient=',R='gwt.codesvr=',S='gwtwebclient',T='startup',U='DUMMY',V=0,W=1,X='iframe',Y='position:absolute; width:0; height:0; border:none; left: -1000px;',Z=' top: -1000px;',$='CSS1Compat',_='<!doctype html>',ab='',bb='<html><head><\/head><body><\/body><\/html>',cb='undefined',db='readystatechange',eb=10,fb='Chrome',gb='eval("',hb='");',ib='script',jb='javascript',kb='moduleStartup',lb='moduleRequested',mb='Failed to load ',nb='head',ob='meta',pb='name',qb='gwtwebclient::',rb='::',sb='gwt:property',tb='content',ub='=',vb='gwt:onPropertyErrorFn',wb='Bad handler "',xb='" for "gwt:onPropertyErrorFn"',yb='gwt:onLoadErrorFn',zb='" for "gwt:onLoadErrorFn"',Ab='#',Bb='?',Cb='/',Db='img',Eb='clear.cache.gif',Fb='baseUrl',Gb='gwtwebclient.nocache.js',Hb='base',Ib='//',Jb='user.agent',Kb='webkit',Lb='safari',Mb='msie',Nb=11,Ob='ie10',Pb=9,Qb='ie9',Rb=8,Sb='ie8',Tb='gecko',Ub='gecko1_8',Vb=2,Wb=3,Xb=4,Yb='selectingPermutation',Zb='gwtwebclient.devmode.js',$b='6143757447205109409E8E4B4B5953F5',_b='616DB373F0C08A308FAA7595CF1774F9',ac='84B5B6FF71219E39FBCAF33FD2B04BCF',bc='9EA5B1320930CAEB74A5FBB6B36A38B0',cc='CDA7348DD6F4462F42A88973CEE8B181',dc=':',ec='.cache.js',fc='loadExternalRefs',gc='end',hc='http:',ic='file:',jc='_gwt_dummy_',kc='__gwtDevModeHook:gwtwebclient',lc='Ignoring non-whitelisted Dev Mode URL: ',mc=':moduleBase';var o=window;var p=document;r(O,P);function q(){var a=o.location.search;return a.indexOf(Q)!=-1||a.indexOf(R)!=-1}

scrappy:gwtwebclient jimdouglas$ 


Is there a button someone can push to rebuild http://samples.gwtproject.org/samples/Showcase/Showcase.html with GWT 2.8.2 to see if that fixes the GWT showcase?


On Thursday, January 24, 2019 at 7:11:56 AM UTC-8, Thad Humphries wrote:
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 "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, send an email to google-web-toolkit+unsubscribe@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.

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

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 wrote:
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+unsubscribe@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.

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

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 "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, send an email to google-web-toolkit+unsubscribe@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.

Re: Error When Calling java method via JSNI - Cannot read property 'apply' of undefined

I found the issue in my code.  The specific issue was how the parameters were defined in "handleJobDefinition".  It's basically a JSNI syntax error.  
$wnd.displayJobDefinitionDialog = $entry(@com.function.operation.Class::handleJobDefinition(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)(jobId, jobType, serviceId));

--should be defined as --

$wnd.displayJobDefinitionDialog = $entry(@com.function.operation.Class::handleJobDefinition(III);

This JSNI reference was extremely helpful:  http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsJSNI.html

On Wednesday, January 23, 2019 at 11:56:30 AM UTC-6, Thomas Broyer wrote:


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 java calls.  However, when I make the call from javascript to GWT and try to pass any parameters from javascript to the GWT method via JSNI, I get a cryptic error that I am unable to trace.


Javascript function  (used this same pattern on multiple occasions without issue)
function openJobDetailsDialog(){
this.displayJobDefinitionDialog("1", "2", "3");
}


GWT methods:

public native void displayJobDefinitionDialog(String jobId, String jobType, String serviceId) /*-{
$wnd.displayJobDefinitionDialog = $entry(@com.function.operation.Class::handleJobDefinition(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)(jobId, jobType, serviceId));


This code calls handleJobDefinition and passes its returned value (which is 'undefined', given that the method's return type is 'void') to $entry(), which wraps it into a function.
So $wnd.displayJobDefinitionDialog is a function, but calling it will fail when $entry() will try to invoke the "wrapped" function (which is 'undefined').

I must say I don't understand your code: where are you expecting the 3 arguments to come from? Java or JS?

If they're supposed to come from Java, and JS would call the method with zero argument, then use:
$wnd.displayJobDefinitionDialog = $entry(function() { @Class:handleJobDefinition(*)(jobId, jobType, serviceId); });

and call it with
window.displayJobDefinitionDIalog();

otherwise, use:
$wnd.displayJobDefinitionDialog = $entry(@Class:handleJobDefinition(*));
or
$wnd.displayJobDefinitionDialog = $entry(function(a, b, c) { @Class:handleJobDefinition(*)(a, b, c) });


and call it as
window.displayJobDefinitionDialog("1", "2", "3");

--
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+unsubscribe@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.

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

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 shelf-signed localhost certificate and ProxyPass to Tomcat 8.5

On Thursday, January 24, 2019 at 1:56:13 AM UTC-5, 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.

--
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+unsubscribe@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.

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

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 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+unsubscribe@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.

Re: Chrome Canary 73.0.3680.0 breaks pretty much ALL 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 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:""

--
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+unsubscribe@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.

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

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+unsubscribe@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.

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 <rob.a.stone@gmail.com>, 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 google-web-toolkit+unsubscribe@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.

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



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 google-web-toolkit+unsubscribe@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.

Wednesday, January 23, 2019

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

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, send an email to google-web-toolkit+unsubscribe@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.

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

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 and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@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.

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

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 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+unsubscribe@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.

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

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 what I've observed.

--
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+unsubscribe@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.

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

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 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, Jim Douglas wrote:
I am seeing breakage with the GWT Showcase:


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 seem to do anything").

On Tuesday, January 22, 2019 at 9:37:19 PM UTC-8, Craig Mitchell wrote:
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 this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@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.