« Bugzilla Issues Index
#224 — Allow RangeError to be used for errors related to non-numeric types
- bug_id:
224
- creation_ts:
2011-11-28 16:35:00 -0800
- short_desc:
Allow RangeError to be used for errors related to non-numeric types
- delta_ts:
2014-07-20 17:25:26 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 16: July 15, 2013 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
VERIFIED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Norbert
- assigned_to:
Allen Wirfs-Brock
- cc:
["d", "waldron.rick"]
- commentid:
510
- comment_count:
0
- who:
Norbert
- bug_when:
2011-11-28 16:35:17 -0800
The description of RangeError currently says: "Indicates a numeric value has exceeded the allowable range." Discussions at and after the TC39 meeting in November 2011 came to the conclusion that we should allow the use of RangeError to also indicate invalid values in non-numeric types. Use cases discussed were language tags, as defined in RFC 5646, or selectors such as "sort" and "search", both used in the ECMAScript Globalization API.
- commentid:
4778
- comment_count:
1
- who:
Domenic Denicola
- bug_when:
2013-08-06 11:23:29 -0700
*** Bug 1730 has been marked as a duplicate of this bug. ***
- commentid:
4793
- comment_count:
2
- who:
Rick Waldron
- bug_when:
2013-08-07 07:30:15 -0700
Updating product and component
- commentid:
4908
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2013-08-15 15:27:16 -0700
fixed in rev17 editor's draft
- commentid:
5168
- comment_count:
4
- who:
Allen Wirfs-Brock
- bug_when:
2013-08-23 08:23:24 -0700
fixed in rev17, August 23, 2013 draft
- commentid:
9413
- comment_count:
5
- who:
Norbert
- bug_when:
2014-07-20 17:25:26 -0700
Verified in rev 26 draft.