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.

---

Since version 4.0.0, when you initialize a time picker to start with the value of 12:00AM it will display the format instead of the actual value (for example hh:mm:ss AM, where 12:00:00 AM should have been displayed).

Demo

I would like a clockpicker something like screenshot below.

It´s easy and fast to use

 

The behavior occurs only when using "hh" format for the hours section. For example: "hh:mm:ss" of "hh:mm". In this case, typing "01" in the hour segment should auto-switch the focus to the minutes segment as this is a valid and complete hour value. However, the focus remains on the hours segment.

For reference, testing the same input ("01") with format "HH:mm" or "h:mm", the focus is moved to the minutes.

The behavior affects the TimePicker and the DateTimePicker components.

Reproduction: https://blazorrepl.telerik.com/cyuFFpFf06hDpzgn20.

Description

The issue is exhibited in the following scenario: a TimePicker bound to a non-nullable DateTime field that is not initialized.
On attempting to change the default time value (only the hours, or the minutes) the TimePicker's validation triggers and after blurring the input shows the default value (12:00 AM). The validation is circumvented by modifying The AM/PM portion of the value. It happens only if the TimePicker uses its default format and only if you type the "A" or "P" letters with the keyboard. Changing AM to PM with the arrow keys does not circumvent the validation.

Steps To Reproduce

Run this REPL example: https://blazorrepl.telerik.com/QJaUFDFw05LBs4Fe22

1. Click the AM part of the value of the first TimePicker.
2. Type "P"

Actual Behavior

The validation is circumvented, because DateValue is updated from 1/1/0001 to the current date.
Re-run the example and try the same with the other TimePicker (which has Format set), as well as with the DateTimePicker.

Expected Behavior

The behavior should be consistent across the board in the different picker components and should not be dependent of the current format.

Browser

All

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

No response