The up/down arrows going up/down works great, but when you are typing the time in directly, it has issues. It seems that if I type the time for hours 2-12, it works exactly as I'd expect. If I type 215, it yields 2:15, if I type 1130, it yields 11:30. But if I type 130, it yields 3:00.

Description

TimePicker bound to a non-nullable DateTime property. User input is marked as invalid, when they change only part of the default TimePicker value.

Steps To Reproduce

1. Run the following REPL example: https://blazorrepl.telerik.com/GpEUOflI50gehA9B54
2. Focus the hour part of the input and type in a number, e.g., 3
3. Blur the TimePicker

Actual Behavior

On beginning to type, the k-invalid class is applied to the TimePicker element. When the use clicks away, the current input value (e.g., 3:00 AM) is replaced with the default value (12:00 AM).

If you type the whole value (e.g., 3:45 AM) and then click away from the component, the k-invalid class is removed and the value is accepted as valid.

Expected Behavior

The k-invalid class should not be applied to the TimePicker in the scenario described above. The used should be able to change only the hour part of the value, or the minutes, without having to type in the whole value.

Browser

All

Last working version of Telerik UI for Blazor (if regression)

8.1.1

When setting time from AM/PM vice-versa (after setting hour and minute), the time is reset.

 

Observed in the demo also;

https://demos.telerik.com/blazor-ui/timepicker/overview

 

This means that the user needs to set AM/PM first, which doesn't follow, as the AM/PM is the right-most UI element.

---

ADMIN EDIT

This is a configuration setup, and not a bug - see the discussion below on the Min and Max features.

---