| Summary: | toLocaleString() doesn't work as it does in Firefox and Chrome | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Philipp Metzler <pp> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ap |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Philipp Metzler
2014-10-31 02:16:32 PDT
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.
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) 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.) I did not set the locale. I'm using OS X with these settings: language: German region: Austria Zahlentrennzeichen: Gruppierung: . Dezimal: , Safari and Webkit seem to ignore these settings. |