Completed
Last Updated: 12 Jan 2024 15:48 by ADMIN
Release 5.1.0 (31 Jan 2024) (R1 2024)
Created by: Stefan
Comments: 2
Category: DateInput
Type: Bug Report
3

The DateInput and all related date/time pickers display 1970/1/1 after programmatic Value clearing and subsequent focus.

The behavior was correct until version 4.6.0 inclusive.

<TelerikDateInput @bind-Value="@DatePickerValue"
                  Width="200px">
</TelerikDateInput>

<TelerikButton OnClick="@( () => DatePickerValue = default )">Clear Value</TelerikButton>

@code {
    private DateTime? DatePickerValue { get; set; } = DateTime.Now;
}

Completed
Last Updated: 29 Oct 2023 07:09 by ADMIN
Release 5.0.0 (15 Nov 2023) (R1 PI1)

Hi,

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

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

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.

Completed
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?

 

Thanks,

 

Chuck

 

Completed
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

Completed
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.
Completed
Last Updated: 28 Jul 2022 13:14 by ADMIN
Release 3.5.0
Created by: David Rhodes
Comments: 0
Category: DateInput
Type: Bug Report
2
We've just noticed that OnChange is not firing on TelerikDateInput (3.4), if I roll back to 3.3.0 it works fine.
Completed
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.
Completed
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.

---

ADMIN EDIT

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">
</TelerikDatePicker>

---

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

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.