You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
If you construct a dayjs object using a string of anything LESS THAN 1883-11-18 12:00:00, meaning 1883-11-18 11:59:59 and below the object will have an unexpected time often being 27:18, see:
Expected behavior
A clear and concise description of what you expected to happen.
Time In = Time Out (obviously unless the timezone changes or something.
Information
Day.js Version: 1.11.10
OS: macOS 14.4 (23E214)
Browser: Chrome 123.0.6312.59
Time zone: Phoenix, its MST, but we don't observe Daylight Saving TIme.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
If you construct a dayjs object using a string of anything LESS THAN
1883-11-18 12:00:00
, meaning1883-11-18 11:59:59
and below the object will have an unexpected time often being27:18
, see:It seems like this could be due to a significant historical event...
see: https://chicagology.com/transportation/timeconvention/#:~:text=At%2012%20o%E2%80%99clock%20noon%20yesterday
but it kinda also seems like its happening when it shouldn't (like with UTC time)
see: https://codesandbox.io/p/sandbox/dayjs-parse-utc-forked-ltsyjn
Expected behavior
A clear and concise description of what you expected to happen.
Time In = Time Out (obviously unless the timezone changes or something.
Information
The text was updated successfully, but these errors were encountered: