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

Re: All ECMAScript attributes should be non-configurable

From: Alex Russell <slightlyoff@google.com>
Date: Wed, 28 Sep 2011 19:44:58 -0700
Message-ID: <CANr5HFX=gMsM07jxSEgG_b8-frxxuD97jXRT78RSMkED39auWQ@mail.gmail.com>
To: David Bruant <david.bruant@labri.fr>
Cc: public-script-coord@w3.org
I hate this idea.

On Fri, Sep 23, 2011 at 12:31 PM, David Bruant <david.bruant@labri.fr> wrote:
> Hi,
>
> In the current form of WebIDL, if i run the following code (in a
> WebIDL-compliant environment):
> -----
> var o = Event.prototype;
> delete o.currentTarget; // works with any other attributes
> -----
> Then, all events afterward will not have a currentTarget property (since
> it's gone from the interface).
> In the DOM event spec, "currentTarget" is defined as an attribute on the
> Event.prototype object. This property must be a configurable (since not
> [[Unforgeable]]). Consequently, any script can remove it and events will
> no longer have a currentTarget property which is not what anyone want.
>
> Consequently, I would suggest to consider all attributes to be
> non-configurable regardless of [[Unforgeab(le)]]-ility.
>
> David
>
>
Received on Thursday, 29 September 2011 02:46:04 UTC

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