[pickers] TimePicker minTime prop not allowing to pick the minimum time

[guna81]

Steps to reproduce

Link to live example: https://codesandbox.io/p/sandbox/mui-time-picker-mintime-issue-xlnqhf

Steps:

1. Select the hour and minutes that specified in the minTime prop in the time picker

Current behavior

Couldn't able to select the time that is given in the minTime prop of the TimPicker.

Expected behavior

Should be able to select the time that is given in the minTime prop of the TimPicker.

Context

When I am trying to pick the minimum time of the picker that I mentioned in the minTime props, I am getting an error behavior.
eg. I am setting 6:00 as a minimum, but if I select 6:00 in the picker, I will get an error in the picker.

Your environment

npx @mui/envinfo

  System:
    OS: Ubuntu 22.04.4 LTS
  Binaries:
    node: v18.20.4
    npm: 10.7.0
  Browsers:
    Chrome: Version 125.0.6422.112 (Official Build) (64-bit)
  npmPackages:
    "@emotion/react": "latest",
    "@emotion/styled": "latest",
    "@mui/material": "latest",
    "@mui/x-date-pickers": "latest",
    "dayjs": "^1.11.10",
    "react": "latest",
    "react-dom": "latest"

Search keywords: time-picker, validation, minTime

[noraleonte]

Hey @guna81 👋

You should be able to pass a correct minTime to the picker if you also set the seconds to 0 (otherwise its value will always be the current exact date and time, with just the hour and minutes modified). Or you can just pass a string value specifying the time, just like here

mintime.mp4

Hope this helps 😄

[guna81]

Hi @noraleonte,

I tried to set second as 0, now it seems fine. I didn't know this minTime also using current time for second value.
Thank you for you help.

[michelengelen]

@noraleonte should we add a recipe/example or callout to the docs for this? Feels like this might not be clear enough!

[noraleonte]

@michelengelen We could!

@guna81 Happy to hear it works! It's something specific to dayjs though. Calling dayjs() gives you the current time, and setting the hour and minutes works, but leaves the seconds unchanged 🙈 That's why depending on when you open the picker the minTime is actually 06:00:xx where the xx is taken from the current time

[LukasTy]

@noraleonte @michelengelen Are you sure that we are missing any documentation in this regard? 🤔
It's just the nature of how specific APIs behave.
In our validation example we already use the startOf function to avoid such issues. 🤔
What extra would you add? 🤷