Open simjoeweb opened 3 months ago
Hey @simjoeweb and thanks for raising this. I can confirm the bug and will add this to the board for the team to have a look!
I suspect this behavior occurs because, at the moment the focus shifts to the digital clock view, the current value is something like 01 02 2024 hh mm aa
, an invalid value. As a result, it falls back to the current date, which is the expected behavior.
Notice that the behavior is the same if you select a time in the popup with empty date values. Also the opposite case: by setting time values from the field and then date values from the calendar, it will ignore the inputed value and use its default
Since we can't parse date and time separately, we must have default values to cover those cases.
@michelengelen Hey Michel! Any news on this? It this an expected behavior or this is considered a bug?
Steps to reproduce
Link to live example: (required)
It can be reproduced on the official website, for any DateTimeRangePicker.
Current behavior
Steps:
The date you manually entered is now today's date.
Expected behavior
It should keep the date you manually entered.
Context
No response
Your environment
``` Don't forget to mention which browser you used. Output from `npx @mui/envinfo` goes here. ```npx @mui/envinfo
Search keywords: date time range picker bug