W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

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

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Thu, 04 Dec 2014 02:58:46 -0800
Message-ID: <54803E66.9060703@mit.edu>
To: "Mark S. Miller" <erights@google.com>
CC: es-discuss <es-discuss@mozilla.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>
On 11/30/14, 6:12 PM, Mark S. Miller wrote:
> On Sun, Nov 30, 2014 at 12:21 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> Per spec ES6, it seems to me like attempting to define a non-configurable
>> property on a WindowProxy should throw and getting a property descriptor for
>> a non-configurable property that got defined on the Window (e.g. via "var")
>> should report it as configurable.
> Yes, both of these conclusions are correct.

OK.  What do we do if we discover that throwing from the defineProperty 
call with a non-configurable property descriptor is not web-compatible? 
  I'm going to try doing it in Firefox, and would welcome other UAs 
doing it ASAP to figure out whether we're in that situation.

Received on Thursday, 4 December 2014 10:59:18 UTC

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