Last Updated: 13 Sep 2023 11:10 by Indra
This issue is for all date inputs when having a higher latency (physical distance between the server and the end-user) the value of the date inputs is not correct. 
Last Updated: 11 Sep 2023 13:12 by ADMIN
To reproduce:

move focus to a DateInput (whole date input is in focus)

Type in 01 into the DateInput, and the caret will move to the end, but no value filled.
Last Updated: 06 Mar 2023 10:01 by ADMIN
Release 4.1.0 (15/03/2023)

Using Telerik Blazor 4.0.1.  Previously on 3.5.0, there were no issues.  The only other difference is .NET 7.0.


Create a blank Telerik Blazor Server project and use the attached index.razor.  In the OnInitialized, there are two lines that set the DateTime.  The first one works but the second one results in the TelerikDateInput field showing h:mm AM instead of 12:00 AM.


Am I doing something wrong?  If so, what changed from 3.5 to experience this?






Last Updated: 20 Dec 2022 15:07 by ADMIN
Release 4.0.0 (18 Jan 2023) (R1 2023)

Currently, if the component has DebounceDelay and loses focus before the delay has passed, the Blur event is fired before the ValueChanged event. 

This bug extends to DateInput, DatePicker, DateTimePicker, and DateRangePicker

Last Updated: 09 Dec 2022 11:19 by ADMIN
Deleting a date segment clears the entire date and automatically focuses on the last date segment.
Last Updated: 21 Nov 2022 15:17 by David

If you use the FloatingLabel, when you tab into the DateInput control, the cursor is set at the very end of the text of the date format. However, if you do not use the FloatingLabel, and you tab into the DateInput control, the placeholder text is selected.

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




The report is initially opened for DateInput, however, it also targets the rest of the date pickers that are compatible with FloatingLabel.

Last Updated: 09 Sep 2022 11:10 by ADMIN
Release 3.6.0 (14 Sep 2022) (R3 2022)
I found that I cannot capture the OnBlur event.
Last Updated: 28 Jul 2022 13:14 by ADMIN
Release 3.5.0
Created by: David Rhodes
Comments: 0
Category: DateInput
Type: Bug Report
We've just noticed that OnChange is not firing on TelerikDateInput (3.4), if I roll back to 3.3.0 it works fine.
Last Updated: 14 Feb 2022 21:11 by ADMIN
Release 3.0.0
DatePicker loses focus when used as data editor in the Grid and the input date starts with 0, for example 05/05/2020. As attached file, you can see a screen recording of the issue.
Last Updated: 01 Feb 2022 16:02 by ADMIN

If you use the format "yyyy-MM-dd" type in a full value and go back to change the year part the focus changes to the month part.

For example enter 2022-01-10 and then go back with the mouse to the year part. Type in 20. The focus then changes to the month part before completing the year part.

This happens with other formats as well when you use MM. The leading zero seems to screw things up. If you play around with the control and changing stuff you will notice that the focus function does not work.


Last Updated: 18 Nov 2021 09:28 by ADMIN
Release 2.30.0

Create the WebAssembly CRUD example from the New Project Wizard and go to the Form page.

Type a year in the date picker. Do not remove the focus and type another year. After doing this a few times the input visibly lags and the form becomes slow.



A potential workaround could be to disable the pointer events so that the users will have a harder time focusing the input so they are more likely to use the drodown to choose dates:

   .k-datepicker .k-dateinput input {
        pointer-events: none;

another approach is to avoid the two-way binding that happens on every keystroke, and use the OnChange event to update the model, for example:

<TelerikDatePicker Value="@person.StartDate"
                   OnChange="@( (object dt) => person.StartDate = (DateTime)dt )"
                   ValueExpression="@( () => person.StartDate )"
                   Width="100%" Id="StartDateDP">


Last Updated: 05 Aug 2021 14:30 by ADMIN


This is easily viewable in your demos.  Using Safari, go to:


Try to use keyboard arrows left and right and up/down to change date.  It doesn't hold the selected date part.  

Works fine in Chrome / Firefox.

Last Updated: 13 Mar 2020 14:15 by ADMIN
Release 2.9.0
Created by: Jamie
Comments: 3
Category: DateInput
Type: Bug Report

Recreational steps:

1. Typed "05"

2. Typed "right arrow" (select month part)

3. Typed "03"

4. Typed "right arrow" (select year part)

5. Tried typing "2020"... but as you can see things went strangely.