Re: FlexJS New errors in Closure Compiler

2017-08-21 Thread Alex Harui
I didn't have as much time as I hoped. You can try turning off CompilerOptions.flowSensitiveInlineVariables And/or CompilerOptions.setNewTypeInference The "step limit" is set to 800,000. It could just be that some code goes through that many "instructions". HTH, -Alex On 8/20/17, 10:05 AM,

Re: Work around Chrome bug?

2017-08-21 Thread Harbs
Modern versions of Opera use Blink and its support is probably pretty analogous to Chrome. The fix looks like this: override public function set width(value:Number):void{ contentContainer.width = value; // needed until https://bugs.

Re: FlexJS New errors in Closure Compiler

2017-08-21 Thread Harbs
I’ll try playing with this later. I don’t have a lot of time today so I’ll see when I get to it. I’ll try connecting with you tomorrow if you have time. > On Aug 21, 2017, at 10:00 AM, Alex Harui wrote: > > I didn't have as much time as I hoped. > > You can try turning off CompilerOptions.flo

Re: Work around Chrome bug?

2017-08-21 Thread Alex Harui
How many JS files are affected? If it is only a few and you think it is a bug that will be fixed, then it is probably better to just monkey patch your JS files. It would be a good test case for making sure we've made it easy enough to do such a thing. You should be able to set up a folder struct

[FlexJS] ManualTests updates

2017-08-21 Thread Greg Dove
I just made some changes in manual tests, including updates to the ant scripts to be more consistent with the ant scripts in the regular examples. I fixed a couple of issues in the GenericTests and renamed it to UnitTests and also added a maven build for that project. It should be easy to add maven