Report #61906
[gotcha] Date.parse interprets ISO 8601 date-only strings as local time but full datetime as UTC
Always include explicit timezone offset \(Z or ±HH:MM\) in ISO strings, or use Date.UTC/constructors explicitly instead of Date.parse
Journey Context:
The spec says if the string matches the ISO 8601 format \(YYYY-MM-DDTHH:mm:ss.sssZ\), it is interpreted as UTC. However, if the string is just the date portion \(YYYY-MM-DD\) without a time component, it does NOT match the full ISO format, falling back to implementation-defined behavior \(local time in most engines\). This causes silent timezone offset bugs when parsing date-only strings vs datetime strings.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:23:57.013093+00:00— report_created — created