OK. This is now fixed. Anyone have thoughts on performance checking to ensure that future performance degradation is caught?
On Nov 18, 2015, at 7:53 AM, Alex Harui <aha...@adobe.com> wrote: > 2) TLF Performance > https://issues.apache.org/jira/browse/FLEX-34769 > > I’d like to get an update from Harbs. I haven’t spent any serious > thinking on the issue, but my recollection is that there is some snippet > of code we could disable or enable with a flag so folks can get old > behavior back if they don’t need whatever that new behavior was meant to > solve (which I think may have been related to table support).
