DateJS: Evolved. An updated, bug fixed, and actively maintained continuation of DateJS
Other
354
stars
79
forks
source link
Datejs 1.0.0-rc3 has inconsistent timezone behavior between Date().parse().set({ hour: 0 }).toISOString() and .toString("yyyy-MM-ddTHH:mm:ss.sssZ") for certain datestrings #254
Datejs 1.0.0-rc3 has inconsistent timezone behavior between Date().parse().set({ hour: 0 }).toISOString() and .toString("yyyy-MM-ddTHH:mm:ss.sssZ") for certain datestrings
2009-07-31T00:00:00.000Z is one known example, which outputs as
2009-07-30T23:00:00.000Z with .set({ hour: 0 }).toISOString()
2009-07-31T01:00:00.000Z with .toString() but is fixed with .set({ hour: 0 })
Karma/chai unit test attached - tested in OSX Phantomjs, Chrome, Safari
Datejs 1.0.0-rc3 has inconsistent timezone behavior between Date().parse().set({ hour: 0 }).toISOString() and .toString("yyyy-MM-ddTHH:mm:ss.sssZ") for certain datestrings
2009-07-31T00:00:00.000Z
is one known example, which outputs as2009-07-30T23:00:00.000Z
with .set({ hour: 0 }).toISOString()2009-07-31T01:00:00.000Z
with .toString() but is fixed with .set({ hour: 0 })Karma/chai unit test attached - tested in OSX Phantomjs, Chrome, Safari