Re: All ECMAScript attributes should be non-configurable

• From: David Bruant <david.bruant@labri.fr>
• Date: Sat, 24 Sep 2011 02:54:10 +0200
• To: Brendan Eich <brendan@mozilla.org>
• CC: public-script-coord@w3.org
• Message-ID: <4E7D2A32.9070801@labri.fr>

Le 24/09/2011 02:52, Brendan Eich a écrit :
> On Sep 23, 2011, at 3:53 PM, David Bruant wrote:
>
>> Currently, on Chrome and Opera (12), event attributes are configurable
>> own properties (data in the former, accessor in the latter).
>> Consequently, the freedom to prevent all events to have a "type" or
>> "target" attribute doesn't exist by design.
>> Do anyone miss that freedom? In other words, are there use cases of
>> wanting this freedom at all or is it just a side-effect of putting
>> properties on the prototype and defaulting to configurable=true because
>> a choice has to be made?
> The "own" vs. prototype design is intentional. The non-configurable is too.
What is the rational behind each of these decisions?

David

Received on Saturday, 24 September 2011 00:54:40 UTC