« Bugzilla Issues Index
#1972 — 26.1.8, Reflect.hasOwn(): unusual evaluation order
- bug_id:
1972
- creation_ts:
2013-09-29 04:59:00 -0700
- short_desc:
26.1.8, Reflect.hasOwn(): unusual evaluation order
- delta_ts:
2013-10-29 09:45:57 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 19: September 27, 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:
5646
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-09-29 04:59:32 -0700
Steps 1-2 and steps 3-4 should be reversed, the current evaluation order is unusual. I don't think the backwards compatibility issue (*) in 19.1.4.2 Object.prototype.hasOwnProperty() needs to applied for Reflect.hasOwn(), too. Consistency with 26.1.7 Reflect.has() seems to be more important.
(*) It's not even a real backwards compatibility issue, e.g. V8 doesn't follow the ES5/6 spec for Object.prototype.hasOwnProperty() and no websites seem to break because of this...
- commentid:
5969
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-10-24 15:07:04 -0700
I agree, internal consistency among the Reflect functions is probably more important.
Fixed in rev20 editor's draft
- commentid:
6115
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-10-29 09:45:57 -0700
fixed in rev20 draft, Oct. 28, 2013