This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27361 - [Unforgeable] and "[[Enumerable]]: true"
Summary: [Unforgeable] and "[[Enumerable]]: true"
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 29383
  Show dependency tree / graph
 
Reported: 2014-11-18 15:48 UTC by Simon Pieters
Modified: 2016-01-29 01:58 UTC (History)
5 users (show)

See Also:

Attachments

Description Simon Pieters 2014-11-18 15:48:24 UTC 
http://heycam.github.io/webidl/#es-platform-objects

[[
[[Enumerable]]: true
]]

Can we make toString, toJSON and valueOf for [Unforgeable] be not enumerable? It seems annoying to have them enumerated for e.g. Location.
Comment 1 Boris Zbarsky 2014-11-18 15:58:42 UTC 
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).
Comment 2 Anne 2016-01-29 01:58:23 UTC 
I have fixed this in https://github.com/annevk/html-cross-origin-objects/issues/19 which should at some point soon make its way into the HTML standard. If we do want these enumerable after all please let me know.

Closing this since we'll remove Unforgeable for interfaces from IDL.