138244 2014-10-31 02:16:32 -0700 toLocaleString() doesn't work as it does in Firefox and Chrome 2014-11-02 21:54:59 -0800 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 77018 P2 Normal --- 1 pp webkit-unassigned ap oldest_to_newest 1045253 0 pp 2014-10-31 02:16:32 -0700 parseInt( '1000' ).toLocaleString() Result in Safari: 1.000 Result in Firefox und Chrome: 1.111 parseFloat( '1000.33' ).toLocaleString() Result in Safari: 1000.33 Result in FF und Chrome: 1.000,33 1045589 1 ap 2014-11-02 01:00:43 -0800 Which locale were you testing under, and how did you set it? From these results, it looks like entirely different locales were used by different browsers. > Result in Safari: 1.000 > Result in Firefox und Chrome: 1.111 It seems unlikely that values are actually different like this. 1045624 2 pp 2014-11-02 11:24:13 -0800 Sorry - there were some typos. It's like this: As I'm in Austria the browsers should use the de_AT locale. parseInt( '1000' ).toLocaleString() Result in Safari: 1000 (the thousands separator is missing) Result in Firefox und Chrome: 1.000 (correct with thousands separator) parseFloat( '1000.33' ).toLocaleString() Result in Safari: 1000.33 (the thousands separator is missing) Result in FF und Chrome: 1.000,33 (correct with thousands separator and comma as decimal mark) 1045625 3 pp 2014-11-02 11:25:47 -0800 Result in Safari: 1000.33 (the thousands separator is missing AND the wrong decimal mark is being used. It's a point instead of a comma.) 1045632 4 pp 2014-11-02 13:23:24 -0800 I did not set the locale. 1045633 5 pp 2014-11-02 13:30:11 -0800 I'm using OS X with these settings: language: German region: Austria Zahlentrennzeichen: Gruppierung: . Dezimal: , Safari and Webkit seem to ignore these settings. 1045655 6 ap 2014-11-02 21:54:59 -0800 Ugh, I somehow didn't realize that Number.toLocaleString does not take locale into consideration at all in WebKit :( *** This bug has been marked as a duplicate of bug 77018 ***