### Bug report
When the TimePicker's type is "modern", the "min" and "max" options cannot be set dynamically through the min(), max(), and setOptions() methods.
### Reproduction of the problem
1. Define the TimePicker with componentType: "modern".
2. Set its "min" and "max" values through the min() and max() options.
3. The "min" and "max" values are not visually updated.
A Dojo sample for reproduction: https://dojo.telerik.com/OXAqUYiw
### Expected/desired behavior
The "min" and "max" values must be dynamically updated when the TimePicker's type is "modern".
### Workaround
let timeView = $("#timepicker").data("kendoTimePicker").timeView;
timeView.options.specifiedRange = true;
timeView.options.min = new Date(2024, 0, 1, 9, 00, 00);
timeView.options.max = new Date(2024, 0, 1, 22, 00, 00);
timeView._updateRanges();
### Bug Report
Picker TagHelpers do not set the "value" attribute in conjunction with the "for" attribute.
### Reproduction of the problem
1. Create a model with a nullable DateTime property:
public class MyModel
{
public DateTime? Birthday { get; set; }
}
2. Declare either a DatePickerFor, DateInputFor, or TimePickerFor TagHelpers and set an initial value:
@model OrderViewModel
<kendo-dateinput for="OrderDate" value="DateTime.Now">
...
</kendo-dateinput>
3. Notice, that the value has not been assigned accordingly.
This behavior is not consistent with the HTMLHelper, as the Value() attribute is taken more predominantly when the PickerFor HtmlHelper is utilized:
@(Html.Kendo().DatePickerFor(m => m.ShippedDate) .Value(DateTime.Today) )
Currently, the DatePicker can be set to read-only mode by adding the "readonly" attribute through the HtmlAttributes() option or by calling the client-side readonly() method.
Is it possible to implement a built-in Readonly() option, so the DatePicker is initialized as read-only? For example:
@(Html.Kendo().DatePickerFor(m => m.StratDate)
.Readonly(true)
)