« Bugzilla Issues Index
#1153 — 21.1.3.3: codePointAt: `undefined` vs. `NaN` return value
- bug_id:
1153
- creation_ts:
2012-12-19 09:28:00 -0800
- short_desc:
21.1.3.3: codePointAt: `undefined` vs. `NaN` return value
- delta_ts:
2013-09-27 14:47:08 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 12: November 22, 2012 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- cc:
["ecmascriptbugs", "mathias"]
- commentid:
3045
- comment_count:
0
- who:
André Bargull
- bug_when:
2012-12-19 09:28:45 -0800
Step 7 returns `undefined` for invalid positions, but per introductory paragraph `NaN` should be returned in that case.
- commentid:
3073
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2012-12-21 12:37:05 -0800
Yes, Norbert needs to confirm whether this should be NaN (consistent with charCodeAt) or undefined (consistent with other missing element access)
- commentid:
5412
- comment_count:
2
- who:
Mathias Bynens
- bug_when:
2013-09-20 12:59:58 -0700
*** Bug 1902 has been marked as a duplicate of this bug. ***
- commentid:
5421
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2013-09-24 17:52:01 -0700
comment fixed in rev19 editor's draft
(this is why we try to avoid redundant informative text)
- commentid:
5517
- comment_count:
4
- who:
Allen Wirfs-Brock
- bug_when:
2013-09-27 14:47:08 -0700
fixed in rev19