W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2015

Re: Figuring out the behavior of WindowProxy in the face of non-configurable properties

From: Brendan Eich <brendan@mozilla.org>
Date: Tue, 27 Jan 2015 19:22:01 -0800
Message-ID: <54C855D9.7020409@mozilla.org>
To: "Mark S. Miller" <erights@google.com>
CC: Boris Zbarsky <bzbarsky@mit.edu>, Domenic Denicola <domenic@domenicdenicola.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
Mark S. Miller wrote:
> The reason why the intent is unwarranted is that the descriptor omits 
> "configurable:" rather than explicitly saying "configurable: true". If 
> the owner object already has a configurable own property of the same 
> name, then a defineProperty where the "configurable:" is omitted 
> defines an own property preserving the configurability of the original 
> own property.

Wild, and genius. How many more narrow escapes can we make and keep both 
web compat and integrity? :-P

Is there any downside? What is the bad case that observably changes 
behavior, if any (not involving proxies)? I'm too tired to search the 
state space right now, throwing this out as a challenge.

Received on Wednesday, 28 January 2015 03:22:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC