« Bugzilla Issues Index
#62 — legacy bugs in Array toLocaleString algorithm v15.4.4.3
- bug_id:
62
- creation_ts:
2011-03-11 10:26:00 -0800
- short_desc:
legacy bugs in Array toLocaleString algorithm v15.4.4.3
- delta_ts:
2015-10-02 13:34:23 -0700
- product:
ECMA-262, Editions 5 and 5.1
- component:
technical content
- version:
Edition 5.1
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- bug_file_loc:
https://mail.mozilla.org/pipermail/es5-discuss/2011-March/003950.html
- priority:
Normal
- bug_severity:
normal
- blocked:
149
- everconfirmed:
true
- reporter:
Allen Wirfs-Brock
- assigned_to:
Allen Wirfs-Brock
- cc:
brterlso
- commentid:
141
- comment_count:
0
- who:
Allen Wirfs-Brock
- bug_when:
2011-03-11 10:26:04 -0800
There are two bugs that exist in ES3 and which were carried forward into ES5:
1) the calls to toLocaleString in steps 8.d and 10.d.iv incorrectly assume that the return value will be a string. ToString should be applied to their results.
2) The this value passed in the above calls should be the original element value (firstElement and nextElement, respectively) rather than elementObject.
The second bug is mostly editorial, but may be observable is the toLocaleString method of Boolean/Number/String.prototype is set to a strict mode function.
There may be some behavioral differences among current browsers for issue 1 but both FF and IE do the implicit ToString and that behavior seems most consistent with other situations in the specificati
- commentid:
575
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2012-01-12 12:16:16 -0800
set IN_PROGRESS to indicated this should go into ES5.1 Errata.
- commentid:
14717
- comment_count:
2
- who:
Brian Terlson
- bug_when:
2015-10-02 13:33:33 -0700
Fixed in ES2015.