Last Updated: 23 Feb 2024 10:59 by ADMIN
Created on: 05 Sep 2023 13:51
Category: DateInput
Type: Bug Report
When the whole DateInput receives focus, and the AllowCaretMode parameter is set to true, you cannot input a value
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.
This item is a duplicate of an already existing item. You can find the original item here:
Posted on: 12 Oct 2023 19:51

I came here looking to see if this was reported, as we are experiencing the exact same issue.

As mentioned in the comments, this can be reproduced without setting AllowCaretMode to true. Our testing has also identified other components that have the same issue, not just the DateInput component (some use the DateInput as part of a composit component, I'm sure, but there is at least one other). Here are the places our testers were able to reproduce the issue so far:

  • DateInput
  • DatePicker (used directly or when used indirectly, such as in the Grid Filter Row)
  • DateTimePicker (used directly or when used indirectly, such as in the Grid Filter Row)
  • TimePicker
  • NumericTextBox

I'm assuming the MaskedTextBox will also have the same issue, but we haven't done much testing there.

To give you an idea of how important this is, picture tabular layout with a bunch of NumericTextBoxes, similar to a basic spreadsheet with 5 columns and 10 rows. The user needs to enter fields in each textbox, one after another. This is likely done with the tab key and the numeric keypad, as there's quite a bit of data entry. On an average desktop computer, the issue can be reproduced about 20% of the time. There are 50 inputs on this form, so the data will be invalid in approximately 10 of the 50 fields. From our users' perspective, this is unacceptable and is basically unusable.

We're also pretty late in testing and do not have time for any major changes to the project. A fix or workaround is urgently needed.

Svetoslav Dimitrov
Posted on: 11 Sep 2023 13:12

Hello Indra,

Thank you for sharing more information and I am sorry that this bug has a noticeable negative impact on your application. 

When we prioritize bug reports one of the main priority indicators that we keep track of is the impact that the bug has on our dev community. This is done through the Votes, the more Votes, the more developers are affected. 

I am sorry to report that opening a private support ticket will not impact the time needed to fix/implement a certain feedback item.

Svetoslav Dimitrov
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!
Posted on: 08 Sep 2023 17:49

If I create a support ticket, will you be able to work on this regardless of number of vote? We will soon deploy our Blazor Server app to production.



Posted on: 08 Sep 2023 13:14

yes so the bug happens for DatePicker Blazor Server version too (default setting without AllowCaretMode ). Not happening in the Web Assembly version (the corresponding REPL page of Telerik Demo page)

In the demo page, select all DatePicker (CTRL + A) so the whole DatePicker is in focus. Then try type in 01 01 2001

This is sample output:


This is the REPL page for that demo page (Web Assembly version)


Posted on: 07 Sep 2023 23:06

Another issue for DateInput Blazor Server version

go to the demo page https://demos.telerik.com/blazor-ui/dateinput/overview focus on the DateInput, press CTRL A to focus on Whole input. try input 01 01 2001, it wont fill the input.

This is not happening in the REPL provided for the demo (Web Assembly version).


BTW the title should be DateInput, not DatePicker