What's more troublesome is that that is inconsistent across different browsers: new Date('1995-12-17T00:00:00') is parsed as UTC on Safari.
According to the specs, strings that do not confirm to ISO 8601 are open for interpretation by difference implementation (like April 13 is April 13 2001 on Chrome, but doesn't work on other browsers). So my first guess was that this string just did not register as ISO 8601 on Chrome and it fell back to its own Interpretation.
I went to the latest ES7 specs and it has changed:
When the time zone offset is absent, date-only forms are interpreted as a UTC time and date-time forms are interpreted as a local time.
So we can have different results based on what version of the browser we are using.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What's more troublesome is that that is inconsistent across different browsers:
new Date('1995-12-17T00:00:00')is parsed as UTC on Safari.According to the specs, strings that do not confirm to ISO 8601 are open for interpretation by difference implementation (like
April 13is April 13 2001 on Chrome, but doesn't work on other browsers). So my first guess was that this string just did not register as ISO 8601 on Chrome and it fell back to its own Interpretation.I went to the latest ES7 specs and it has changed:
So we can have different results based on what version of the browser we are using.