You're quite right, it is the date parsing.
Your 2013 dates lack a leading zero on the month ('1' vs '01').
If you fix that, it will be parsed consistently with your other dates.
FWIW, it seems Chrome is more lax... but there's some more inconsistency,
too. -- Try this in Chrome's console:
- new Date('2013-1-01')
- new Date('2013-01-01')
>From
http://stackoverflow.com/questions/5802461/javascript-which-browsers-support-parsing-of-iso-8601-date-string-with-date-par
Yes, Date.parse is not consistent for different browsers. You could:
- Use Date.UTC instead, which breaks up the date-string into separate
inputs
- Use a wrapper library like jQuery's parseDate
-Tom
On Thursday, September 27, 2012 2:05:45 PM UTC-4, Carl Erik Kopseng wrote:
>
> The first post never showed up, so will try again ...
>
> I created a fiddle that shows a problem that only concerns IE and Firefox.
> Check
> it out here <http://jsfiddle.net/oligofren/HgfVf/10/>. You can see the
> resulting chart from the attached images. As you can see, one version is
> totally wrecked, whereas the other (Chrome) is fine. Both versions are fine
> if the dates are within the same year, but as soon as they cross Jan 1, the
> bug hits IE and Firefox ... Data for both the working version and the buggy
> version can be found in the fiddle.
>
--
You received this message because you are subscribed to the Google Groups
"Google Visualization API" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-visualization-api/-/KmDOP4YhqaoJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-visualization-api?hl=en.
