Home/ Questions/Q 8643339
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T12:00:42+00:00

I tried this in the Chrome JS console, with my locale time zone set

  • 0

I tried this in the Chrome JS console, with my locale time zone set as PST:

(new Date("07-15-2005"))

=> Fri Jul 15 2005 00:00:00 GMT-0700 (PDT)

(new Date("07-15-2005")).getTime();

=> 1121410800000

but….

(new Date("2005-07-15"))

=> Thu Jul 14 2005 17:00:00 GMT-0700 (PDT)

(new Date("2005-07-15")).getTime();

=> 1121385600000

I was expecting string parsing to occur in both. But I can’t make out why when format YYYY-MM-DD is used, it assumes a timezone offset. It’s as if I’m expressing “2005-07-15” in my local TZ, but “07-15-2005” is expressed in UTC.

Is the correct explanation?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The implementation seems to be vendor specific, however looking at the documentation of date parse we see that as of 1.8.5 javascript supports both RFC2822 dates and ISO 8601 dates.

    As per the Date.UTC documentation ISO 8601 dates are assumed to be in UTC time if not otherwise specified and thus the timezone difference is automatically added.

    RFC2822 dates seem to be assumed as local times and as such are not modified.

    • 0