« Bugzilla Issues Index
#1276 — 15.4.3.4: Array.from: the mapfn argument is not used
- bug_id:
1276
- creation_ts:
2013-03-09 07:20:00 -0800
- short_desc:
15.4.3.4: Array.from: the mapfn argument is not used
- delta_ts:
2013-07-15 17:04:00 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 14: March 8, 2013 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Claude Pache
- assigned_to:
Allen Wirfs-Brock
- cc:
waldron.rick
- commentid:
3405
- comment_count:
0
- who:
Claude Pache
- bug_when:
2013-03-09 07:20:09 -0800
Some piece of the algorithm is missing between steps 11.c.ii and 11.c.iii, namely: kvalue = mapfn.call(thisArg, kValue) unless mapfn is undefined.
- commentid:
3406
- comment_count:
1
- who:
Claude Pache
- bug_when:
2013-03-09 07:42:36 -0800
(In reply to comment #0)
I wanted to say: between steps 11.d.ii and 11.d.iii, naturally. Also, the phrase introducing the algorithm ("When the from method is called with argument arrayLike, the following steps are taken") should be amended in order to mention the mapfn and thisArg arguments.
> Some piece of the algorithm is missing between steps 11.c.ii and 11.c.iii,
> namely: kvalue = mapfn.call(thisArg, kValue) unless mapfn is undefined.
- commentid:
4339
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-06-30 13:40:17 -0700
fixed in rev16 editor's draft
- commentid:
4467
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2013-07-15 17:04:00 -0700
fixed in rev16 draft. July 15, 2013