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: Mon, 07 Oct 2013 21:07:46 +0000
To: public-script-coord@w3.org
Message-ID: <bug-21929-3890-b2m5kZ0Hjl@http.www.w3.org/Bugs/Public/>

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
                 CC|                            |travil@microsoft.com

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> ---
Is this behavior for [[DefineOwnProperty]], now basically the same as if the
named properties object were considered non-extensible? e.g., it seems weird to
get this behavior, yet Object.isExtensible() would still say true? If we
changed this to simply mark the option (internally) as preventExtensions()
would that do the trick?

Of course, it's weird to have own properties magically come and go too, so I'm
not sure what's more or less consistent here...?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 7 October 2013 21:07:48 UTC

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