[pickers][DateTimeRangePicker] selecting the same date for the second part of the range does not work as expected

[christopher-wittlinger]

Steps to reproduce

Link to live example: (required)

Steps:

1. Go to the official documentation of Mui-X: https://mui.com/x/react-date-pickers/date-time-range-picker/#use-a-single-input-field
2. Click on today
3. Click on 4, 00, PM
4. Click on today
5. Click on 5, 00, PM

Current behavior

The first time switches to 12:00 PM

Expected behavior

The first time should stick with 4:00 PM and do not jump back to 12:00 PM

Context

No response

Your environment

npx @mui/envinfo

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: DatetimeRange Picker
Order ID: 77969

[christopher-wittlinger]

Here a video detailing the bug:
Screencast from 2024-03-28 08-50-54.webm

[christopher-wittlinger]

I have tried it under Firefox and Chrome

[michelengelen]

@LukasTy It does seem like clicking the previously selected date will reselect the starting range and not even focus the endrange value as well.

It is also broken on the other DateTimeRangePicker components, not only the one with the single input field

[github-actions]

⚠️ This issue has been closed.
If you have a similar problem, please open a new issue and provide details about your specific problem.
If you can provide additional information related to this topic that could help future readers, please feel free to leave a comment.

How did we do @cwittlinger89?
Your experience with our support team matters to us. If you have a moment, please share your thoughts through our brief survey.

[LukasTy]

@cwittlinger89 Thank you for reporting this and trying the new component! 🙏
May I ask you, how do you like it?
Do you see any problems with it, or something missing?
The fix has been merged and will be released in around a week. 😉

[christopher-wittlinger]

@LukasTy
thank you for the swift response regarding the hotfix.

Until now we are using a lot of Mui(x) components and are generally very happy about them. The Datetime Range picker was something we are looking forward to since December, as it is our last non-mui component that we have to fully maintain.

From a first glance we like it, however there is one thing that takes a bit getting used to:

• Our Picker: First Date, Second Date, First Time, Second Time
• Mui Picker: First Date, First Time, Second Date, Second Time

As we have not yet released the mui-picker due to the aforementioned bug, we do not know how our users will react to this change. Generally speaking it would be cool if our methodology would be supported as well.

[christopher-wittlinger]

@LukasTy I could have sworn that it worked earlier with 7.1.0, now it again does not work at all.

[LukasTy]

@cwittlinger89 It shouldn't have worked before the fix, the code is deterministic and will always result in the first day being overridden if the same day is selected.
The only way that selected on the same day will work is if you do not touch the start time (keep it at midnight).

As for your comment regarding the selection flow, I've created a separate issue with more information for it: #12635.
Please feel free to interact with it and thank you for your valuable feedback! 🙏

[christopher-wittlinger]

@cwittlinger89 It shouldn't have worked before the fix, the code is deterministic and will always result in the first day being overridden if the same day is selected. The only way that selected on the same day will work is if you do not touch the start time (keep it at midnight).

When will this fix be live? Because under 7.1.0 it does not work.

As for your comment regarding the selection flow, I've created a separate issue with more information for it: #12635. Please feel free to interact with it and thank you for your valuable feedback! 🙏

I will

[LukasTy]

When will this fix be live? Because under 7.1.0 it does not work.

With the next release that we usually do every Thursday (it is sometimes delayed in case of a complex release-changelog).