« Bugzilla Issues Index
#2183 — 9.5, 26.2.2.1.1: Internal state of revoked Proxies does not match description
- bug_id:
2183
- creation_ts:
2013-11-04 07:57:00 -0800
- short_desc:
9.5, 26.2.2.1.1: Internal state of revoked Proxies does not match description
- delta_ts:
2013-11-08 13:08:47 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 20: October 28, 2013 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
6423
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-11-04 07:57:58 -0800
9.5 Proxy Object Internal Methods and Internal Slots, 1st paragraph, 3rd paragraph:
> Every proxy object also has an internal slot called [[ProxyTarget]] whose value is either an object or the null value. [...]
> When a proxy is revoked, its [[ProxyHander]] internal slot is set to a special revoked proxy handler object and its [[ProxyTarget]] internal slot is set to null. [...]
Description needs to be updated to state that `[[ProxyHander]]` and `[[ProxyTarget]]` are both set to `undefined`.
- commentid:
6443
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-11-04 08:52:27 -0800
fixed in rev21 editor's draft
I actually left that text alone and changed to using null as the value that [[ProxyTarget]] and [[ProxyHandler]] get set to upon revocation.
That was the original intent.
However, I don't believe that this is actually an observable difference.
- commentid:
6510
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-11-08 13:08:47 -0800
fixed in rev21 draft