« Bugzilla Issues Index
#209 — Object.seal/freeze should not tough private named properties
- bug_id:
209
- creation_ts:
2011-09-27 13:35:00 -0700
- short_desc:
Object.seal/freeze should not tough private named properties
- delta_ts:
2013-08-15 15:51:38 -0700
- product:
Draft for 6th Edition
- component:
normative change from ES5.x
- version:
Rev 3: September 23, 2011 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
INVALID
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Allen Wirfs-Brock
- assigned_to:
Allen Wirfs-Brock
- cc:
erights
- commentid:
489
- comment_count:
0
- who:
Allen Wirfs-Brock
- bug_when:
2011-09-27 13:35:38 -0700
As a reflection operations they should not modify the attributes of properties whose keys are private named objects.
- commentid:
2556
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2012-11-22 13:48:20 -0800
Mark,
I believe you originally suggested this. A questions:
For freeze, should this apply to both the [[Configurable]] and [[Writable]] attributes? I can understand why an internal implementation might need to keep its private state writable, but would it really need to make sure it stays configurable? Does it need to apply to seal, at all?
- commentid:
4912
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-08-15 15:51:38 -0700
since we don't have private symbols in ES6 this is no longer an issue.