Just to clarify -- On Fri, Aug 31, 2012 at 11:28 AM, Kevin Reid <[email protected]> wrote:
> forceES5 should not be used for actual applications as it is potentially > insecure. > The reason this is true is that, when you specify forceES5, we take advantage of the browser's ES5 features whether they are *absolutely* complete or not. It is for testing and evaluation. If you are *sure* that your clients are using browsers on which our ES5 implementation is solid (which you can tell by running in debug mode and looking at the console messages), then ES5 should work. Our autoswitching logic to decide whether to use ES5 features or emulate via rewriting is sort of out of date at the moment, but our actual ES5 implementation is well-tested and we are quite confident in its quality. Ihab -- Ihab A.B. Awad, Palo Alto, CA
