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

[Bug 27361] [Unforgeable] and "[[Enumerable]]: true"

From: <bugzilla@jessica.w3.org>
Date: Tue, 18 Nov 2014 15:58:42 +0000
To: public-script-coord@w3.org
Message-ID: <bug-27361-3890-39xg8Oqffs@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27361

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |allen@wirfs-brock.com,
                   |                            |bzbarsky@mit.edu

--- Comment #1 from Boris Zbarsky <bzbarsky@mit.edu> ---
It's technically quite easy to do.

It's not clear to me how it ties in to the current ES thinking on
enumerability.  Allen?  The idea here is that we have some objects we want to
lock down so we're defining non-configurable, non-writable
toString/toJSON/valueOf on them (with some sort of canonical value).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 18 November 2014 15:58:46 UTC

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