W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2011

RE: All ECMAScript attributes should be non-configurable

From: Travis Leithead <travil@microsoft.com>
Date: Fri, 30 Sep 2011 21:18:19 +0000
To: David Bruant <david.bruant@labri.fr>, Erik Arvidsson <arv@chromium.org>
CC: Alex Russell <slightlyoff@google.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <9768D477C67135458BF978A45BCF9B3834CEC0B8@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
>> +IE9 (another example using configurable properties--as accessor properties on the prototypes). We did work around the performance issue using caches, as most sites don't mess with the configurability of the properties.
> What performance issue are you refering to? Brendan's argument was actually that this design was better in terms of performance.

The performance issue was the introduction of ECMAScript5 setters (which much be checked for anywhere in the prototype chain before assigning an own property).

Received on Friday, 30 September 2011 21:18:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:04 UTC