« Bugzilla Issues Index
#4224 — 26.2.2.1 Proxy.revocable: "revoke" as data instead of method property?
- bug_id:
4224
- creation_ts:
2015-03-27 07:07:00 -0700
- short_desc:
26.2.2.1 Proxy.revocable: "revoke" as data instead of method property?
- delta_ts:
2015-04-03 12:35:37 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 36: March 17, 2015 Release Candidate 3
- 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:
13941
- comment_count:
0
- who:
André Bargull
- bug_when:
2015-03-27 07:07:59 -0700
26.2.2.1 Proxy.revocable ( target, handler )
Step 7.
The revoker function is currently installed as a method property, even though it's not really a method but simply a function valued property. (For example it does not have a `this` binding.)
I wonder if it makes sense to replace CreateMethodProperty with CreateDataProperty.
- commentid:
14004
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-04-01 15:12:05 -0700
fixed in rev378 editor's draft
I'm kind of on the fence on this, but making it enumerable can be rationalized as being consistent with what you would get if Proxy.revocable was self-hosted and used an Object Literal to create the result object.
- commentid:
14092
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2015-04-03 12:35:37 -0700
In Rev37