minTime and maxTime doesn't work...

[bluego78]

minTime and maxTime doesn't work...
if you set a new Date() or a string like "07:00:00" not working.

[anniekfifer]

Also experiencing this issue as of recently but not sure for how long. Reproduced using both Date and string inputs, in military format with and without seconds.

[toto22450]

Is there any update on this issue ?

[eglorenzana]

I also have this issue in version 2.8.
I updated directly to version 4.0.1 and it seems to be working.

UPDATE

Trying in version 4.0.1, the input has the attributes min and max accordingly with the minTime prop.

• Using key up and key down work fine.
• If the value is modified by typing the number itself, and by doing that the value results in a non-valid time, the onChange event is not triggered (docs describe onChange event is triggered for valid date only)

Since min and max are set correctly, I am using the :invalid css selector to make the invalid time noticeable, but I haven't find a way to report the error from an event

[marcosilvestroni]

as @eglorenzana reported this bug cannot intercept the error why not add an onError callback? for manage this situation?

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 14 days.

[github-actions]

This issue was closed because it has been stalled for 14 days with no activity.

[youbek]

Agree with @marcosilvestroni. We definitely need an onError callback, for example, I want to disable the Form button when there is invalid input in TimePicker.