BenB
Reputation: 10620
Date.toLocaleString() broken in Chrome?
Date.toLocaleString() returns this in Chrome:
- Mon Jan 18 2010 16:47:42 GMT+1100 (AUS Eastern Daylight Time)
In firefox, it's this:
- Monday, 18 January 2010 4:47:42 PM
Browser version doesn't seem to matter. Anyone have a suggestion on this one?
Upvotes: 1
Views: 2636
Answers (2)
peller
Reputation: 4543
As CMS answered above, these methods can return pretty much anything they want, hopefully in a representation that is readable to someone in that locale (language + cultural conventions) To obtain a particular formatting of a Date, you need to use a library like DateJS or Dojo.
Upvotes: 0
Related Questions
- Does date.toLocaleString have a bug?
- Why Chrome Date .toLocaleString() seems not to use windows.navigator.language?
- Date.toString and Date.toLocaleDateString are inconsistent across Chrome and Firefox?
- Javascript Date.ToLocaleTimeString() doesn't match computer's time format
- How does toLocaleDateString() work in Chrome?
- toLocaleString doesn't seem to work as expected
- Alternative to toLocaleString() for chrome browser
- toLocaleDateString() in Chrome returns the wrong date
- Chrome timeZone option to Date.toLocaleString()
- Chrome, javascript Date and toLocaleString()