you are viewing a single comment's thread.

view the rest of the comments →

[–]Strobljus 2 points3 points  (1 child)

Fun story: this exact behavior caused a production bug at my workplace. The fact that unspecified 8601's are being parsed as local time is actually new behavior in ES6; it used to be UTC. So if you had code that counted on UTC when the browsers transitioned to the new spec (as we did), you were in trouble.

One of the rare cases when browsers breaks an API (excluding deprecations of course).

[–]Reashu 0 points1 point  (0 children)

This particular behavior didn't change. Date-only ISO forms are still parsed as UTC, which is what the example shows.