[pickers] AM/PM field is not disabled when validation fails for the minTime and maxTime properties.

[A-s-h-o-k]

Steps to reproduce

Steps:

import * as React from 'react';
import { DemoContainer } from '@mui/x-date-pickers/internals/demo';
import { AdapterDayjs } from '@mui/x-date-pickers/AdapterDayjs';
import { LocalizationProvider } from '@mui/x-date-pickers/LocalizationProvider';
import { TimePicker } from '@mui/x-date-pickers/TimePicker';
import dayjs from 'dayjs'

export default function BasicTimePicker() {
  return (
    <LocalizationProvider dateAdapter={AdapterDayjs}>
      <DemoContainer components={['TimePicker']}>
        <TimePicker label="Basic time picker" minTime={dayjs().add(8, 'h')}/>
      </DemoContainer>
    </LocalizationProvider>
  );
}

Current behavior

When the AM/PM (12-hour format) option is selected in the time picker, the AM/PM field is not disabled, even if the minTime is set to a later time. This allows users to select 'AM,' even if that time has already passed, while the other fields are working properly.

Expected behavior

When the AM/PM (12-hour format) is selected in the time picker, the AM/PM field should be disabled.

Context

this issue occurs when you pass the ampm prop true to the timepicker

Your environment

npx @mui/envinfo

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

Search keywords: timepicker

[michelengelen]

Thanks for opening an issue for this @A-s-h-o-k ... I could not find a quick solution for this so I will add it to the board for the team to estimate. 👍🏼

[LukasTy]

This issue looks like an already estimated duplicate of #12159.
Closing this one as duplicate in favor of the mentioned issue. 😉