GWT behaves differently in Chrom vs Firefox

Friends: I have an application written using GWT 2.8.2 framework and it behaves differently. The snippet of the GWT code in question is here - (ReferenceError) : L_g_g$ is not defined for (int j = 1; j < nodes.size(); j++) { Node previousNode = nodes.get(j - 1); Node curre

Re: GWT behaves differently in Chrom vs Firefox

Is this in SDM mode? If yes, try turning off incremental compilations. On Mon, Jul 23, 2018 at 9:43 PM, Velusamy Velu wrote: > Friends: > > I have an application written using GWT 2.8.2 framework and it behaves > differently. The snippet of the GWT code in question is here - > (ReferenceError) :

Re: GWT behaves differently in Chrom vs Firefox

Hi Michael I appreciate your recommendation. Yes it's in SDM mode. I don't have the luxury to try your suggestion right away due to my travel. Will try it on my return. I did suspect something to the effect of a cache behind this. Hence I tried clearing and rebuilding, it failed yet. Nothing help

Re: GWT behaves differently in Chrom vs Firefox

clear your temp folder, sdm puts lots of stuff there and sometimes it gets corrupted and you get these kind of errrors. On 24 Jul 2018, 18:53 +0200, Velusamy Velu , wrote: > Hi Michael > > I appreciate your recommendation. Yes it's in SDM mode. I don't have the > luxury to try your suggestion rig

Re: GWT behaves differently in Chrom vs Firefox

Hi Michael: I tried this by Windows > Preferences > General > Workspace > Build and unchecked the "Build automatically" option. It didn't help. Am I doing the right thing? Is there any other option? Thanks Velu On Tuesday, July 24, 2018 at 11:08:00 AM UTC-4, Michael Joyner wrote: > > Is this in

Re: GWT behaves differently in Chrom vs Firefox

> Hi Michael: I tried this by Windows > Preferences > General > Workspace > > Build and unchecked the "Build automatically" option. It didn't help. Am > I doing the right thing? Is there any other option? > GWT SuperDevMode has its own cache that you can clear by visiting the SuperDevMode pag

Re: GWT behaves differently in Chrom vs Firefox

We use Gradle here and we turn off SDM incremental when needed from there. On Mon, Jul 30, 2018 at 2:58 PM, Velusamy Velu wrote: > Hi Michael: I tried this by Windows > Preferences > General > Workspace > > Build and unchecked the "Build automatically" option. It didn't help. Am > I doing the ri

Re: GWT behaves differently in Chrom vs Firefox

Michael & David After clearing the TEMP folder and clearing the compiler caches at localhost:9876 that error message disappeared. Thanks a lot Velusamy K. Velu 614-321-9649 On Mon, Jul 30, 2018 at 3:18 PM Jens wrote: > > Hi Michael: I tried this by Window

Re: GWT behaves differently in Chrom vs Firefox

tasks.withType(org.wisepersist.gradle.plugins.gwt.AbstractGwtActionTask) { args "-noincremental" } gwt { logLevel = 'INFO' maxHeapSize = "2048M"; gwtVersion='2.8.2' modules 'xxx //src += files("build/generated/source/apt/main"); compiler { //ea = false //enable assert statements for testing result

Re: GWT behaves differently in Chrom vs Firefox

Jens: Thank you, it helped. --Velu On Monday, July 30, 2018 at 3:18:12 PM UTC-4, Jens wrote: > > > Hi Michael: I tried this by Windows > Preferences > General > Workspace > >> Build and unchecked the "Build automatically" option. It didn't help. Am >> I doing the right thing? Is there any other

Re: GWT behaves differently in Chrom vs Firefox

Michael: I appreciate you sharing the information. I never considered Gradle to build, may be it's time. Thank You --Velu On Monday, July 30, 2018 at 3:47:30 PM UTC-4, Michael Joyner wrote: > > tasks.withType(org.wisepersist.gradle.plugins.gwt.AbstractGwtActionTask) { > args "-noincremental"