Too many 0 digits in smallest increment input is not triggering error state

[emilyuhde]

If you have a TimePicker with hours and minutes and you want to enter 10:00, enter 10 into the hours input, the TimePicker will move you to the mintes input, then type in 00. After you type the first 0, a leadering 0 is automatically added, but when you type in your next 0, you will have too many digits in the minutes input (000) but the error state isn't triggered. This also happens if you enter other digits after your 0s, say 0001 or 0011. It only triggers the error state for non-zero numbers with too many digits from what I can tell, such as 000111, 0111 or 111.

[emilyuhde]

It would be nice if there was a max length set on the smallest increment of time a TimePicker uses in this case minutes, to avoid the issue by not even allowing more than two digits to be entered in each part of the time.

[wojtekmaj]

Kinda duplicate of #45 / #87.

Since the latter just have been fixed, I believe this issue should be fixed fully in v4.2.0.

[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.