« Bugzilla Issues Index

#209 — Object.seal/freeze should not tough private named properties

As a reflection operations they should not modify the attributes of properties whose keys are private named objects.


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?

since we don't have private symbols in ES6 this is no longer an issue.