« Bugzilla Issues Index
#1407 — 15.7.1.1: `Number(undefined)` no longer returns NaN
- bug_id:
1407
- creation_ts:
2013-04-10 08:23:00 -0700
- short_desc:
15.7.1.1: `Number(undefined)` no longer returns NaN
- delta_ts:
2013-05-14 18:13:05 -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:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
3588
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-04-10 08:23:17 -0700
See step 2 of 15.7.1.1:
> 8. If value is undefined, then let n be +0.
That means `Number(undefined)` will now return 0 instead of NaN.
Also: algorithm steps are mis-numbered
- commentid:
3604
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-04-10 10:14:05 -0700
fixed in rev 15 editor's draft
- commentid:
3872
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-05-14 18:13:05 -0700
resolved in rev 15, May 14, 2013 draft