-
-
Notifications
You must be signed in to change notification settings - Fork 160
Datepicker adds one hour between March 9 and March 29 2025 #1091
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I am experiencing the exact same issue. I believe it is related to Daylight Saving Time (DST) in the U.S., which begins on the second Sunday of March (March 9 in 2025), and DST in Europe, which begins on the last Sunday of March (March 30 in 2025). This specific period seems to be causing issues. What I would expect is that selecting a different date does not change the selected time. EDIT: now, March 10, the following is happening:
|
Just to add some info to this, this seems to only happen if you specify the timezone. If you don't set the timezone and are in that timezone, it works fine. For example, if I set the timezone to 'America/New_York', it subtracts an hour when I click select. However, since I am in that timezone and I don't add the timezone property, it works perfectly. |
Same as #1112 |
Currently having the issue that its subtracting 2 hours from the time in the input?
How can i get it to emit the exact time that was picked instead of converting it? EDIT: IT also has the same behaviour when not defining the timezone prop at all |
Describe the bug
For some reason, when the device's timezone does not match the timezone provided to the datepicker and I select a date between March 9 and March 29 2025, an hour is added to the chosen time. Outside of these dates, there's no issue in the year 2025. The same issue occurs between March 8 and March 28 2026. Haven't tried for following years but the pattern might continue. It also doesn't happen for every combination of device timezone and the timezone provided to the datepicker. Some more investigation would be needed to determine the exact conditions in which the issue occurs.
The issue was already present in v9.0.3, maybe already before. Still present in v11.0.1.
To Reproduce
Expected behavior
The time should be the same as selected.
Screenshots

Desktop & mobile (please complete the following information):
The text was updated successfully, but these errors were encountered: