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: Andreas Rossberg <rossberg@google.com>
Date: Tue, 2 Dec 2014 13:59:32 +0100
Message-ID: <CADjR9NrTogoafmFPPRfQLc=ZwAznm5d52Db9S5LutuSUeg2eYw@mail.gmail.com>
To: "Mark S. Miller" <erights@google.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
On 1 December 2014 at 03:12, Mark S. Miller <erights@google.com> 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.

Can you clarify? Do you mean that it should report properties as
configurable, but still reject attempts to actually reconfigure them?
Also, how would you allow 'var' to even define non-configurable
properties? If you want DefineProperty to throw on any such attempt,
then 'var' semantics would somehow have to bypass the MOP.

> From prior similar experiences, the way to get this fixed quickly is
> to add test262 tests which fail on these violations. All browsers have
> been much quicker to fix breakage that shows up in test262 results
> than to mere bug reports.

Well, let's find a workable semantics first. :)

/Andreas
Received on Tuesday, 2 December 2014 13:00:29 UTC

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