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

[Bug 21929] named properties object should disallow definition of non-configurable properties

From: <bugzilla@jessica.w3.org>
Date: Tue, 08 Oct 2013 07:48:40 +0000
To: public-script-coord@w3.org
Message-ID: <bug-21929-3890-lkBOEc6W3K@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21929

Tom Van Cutsem <tomvc.be@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tomvc.be@gmail.com

--- Comment #4 from Tom Van Cutsem <tomvc.be@gmail.com> ---
(In reply to Travis Leithead [MSFT] from comment #3)
> Is this behavior for [[DefineOwnProperty]], now basically the same as if the
> named properties object were considered non-extensible?

No, an object marked non-extensible cannot acquire new own properties (whether
via [[DefineOwnProperty]] or via some external means). That's what it means to
be non-extensible.

I believe Cameron's fix of simply making [[DefineOwnProperty]] reject any
updates is fine in terms of ES6 invariants. This could be self-hosted as a
proxy that just returns 'false' from its defineOwnProperty trap.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 8 October 2013 07:48:45 UTC

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