[TimeClock] The TimeClock selects the same minutes when selecting the hour

[RavdeepSingh99]

Steps to reproduce

Link to live example: https://codesandbox.io/embed/gjdm36?module=/src/Demo.tsx&fontsize=12

Steps:

1. This is occuring on the mobile or you can also test it on the chrome by toggling the device Inspector tool within the chrome inspect.
2. Select the hour hand
3. You'll see the minutes hand is at the same place as the hour hand

I've tested various versions and found out that this bug started to appear from 7.15 and also exists in the MUI latest version

Recording.2024-11-08.164701.mp4

Current behavior

When clicking on TimeClock for hour selection it automatically select the minutes.

Expected behavior

When clicking on TimeClock for hour selection it shouldn't automatically select the minutes.

Context

No response

Your environment

npx @mui/envinfo

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
  
    System:
    OS: Windows 11 10.0.26100
  Binaries:
    Node: 20.14.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.3 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Chrome: 130.0.6723.117
    Edge: Chromium (130.0.2849.46)
  npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3
    @emotion/styled: ^11.13.0 => 11.13.0
    @mui/core-downloads-tracker:  6.1.6
    @mui/material: ^6.1.6 => 6.1.6
    @mui/private-theming:  6.1.6
    @mui/styled-engine:  6.1.6
    @mui/system:  6.1.6
    @mui/types:  7.2.19
    @mui/utils:  6.1.6
    @mui/x-date-pickers: ^7.22.1 => 7.22.1
    @mui/x-internals:  7.21.0
    @types/react:  18.3.12
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    typescript:  4.9.5

Search keywords: timeclock, timepicker selects the same minutes

[arthurbalduini]

Hello @RavdeepSingh99

Thanks for reporting the issue and providing a rich description.
I can confirm the issue with this behavior and it has been introduced on v7.15.0, more specifically by #14305
We will work on a fix for it and will update here once it's done.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@RavdeepSingh99 How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.