Last Updated: 10 Aug 2021 10:13 by René
Created on: 08 Jan 2021 05:41
Category: UI for Blazor
Type: Bug Report



I have just received some feedback from a client re. the DateInput -Blazor control whereby they are describing the default behaviour as "strange" - and on having a closer look I tend to agree / believe there to be bugs with this.


Please see video and below notes - let me know if there are any workarounds to these things.
I do see there is an existing bug report which may partially cover these issues (DatePicker loses focus when used as data editor in the Grid and the input date starts with 0 (telerik.com)) , however, it seems this is "unplanned" ?


QA Telerik DateInput:

  • Try entering in M =  1 then 1 SLOW = works ok

  • Try entering in M =  1 then 1 FAST = focus moves to the end of the date

  • Try entering 0 in the month or day  = Whole date disappears 
    (Data loss - for in-cell edit mode this is a big deal)

  • Try entering DD = 11 then its ok for 1st edit, but 2nd edit of the DD, 
    then the focus moves to the end????

  • Try entering M = 1, D = 8, Y=2021 without using the mouse 
    (its not possible as 01 would move focus to end of date).... 
    and if you choose to type 01 and its not fast enough, the whole date will disappear on entry of 0


Entering a date without using the mouse to move focus is quite important for big data-entry in grids where you are tabbing or clicking over from field to field in large quantities.



This item is a duplicate of an already existing item. You can find the original item here:
Posted on: 10 Aug 2021 10:13
In an empty DatePicker (i.E. "dd.MM.yyyy" is displayed) typing "01012021" works.  Upon changing the value of a DatePicker (e.g. current Value is "02.02.2021") typing "01012021" does not work.
Posted on: 10 Aug 2021 10:05
This is not the duplicated item but the other one is.  This item is more general. The other item is only about using DateInputs in Grids.
Posted on: 10 Aug 2021 10:03

If you use the format "dd.MM.yyyy" to get "01.01.2021"  users want to type "01012021" but this does not work.
The fastest way to type that date for now is typing "1.1.2021" but users won't use different typing patterns for one digit and two digit days/month.

Please make sure that this bug will be fixed for the next release.

In combination with this bug https://feedback.telerik.com/blazor/1523288-datepicker-won-t-let-the-user-type-in-a-year (because we use "dd.MM.yy" format a lot) typing in DatePicker is more or less impossible.

Nadezhda Tacheva
Posted on: 08 Jan 2021 16:53
Hi Philip,

Indeed if you are dealing with big data input having to use the mouse is not the most convenient way. However, the input supports keyboard navigation and pressing the left/right arrow will allow you to switch between day, month and year fields (you can test that in the Grid overview demo, I've recorded the video on that page).

If you type, for example, 1 for the month, the focus will still be at the month field to let you type one more digit for a valid two-digit month (10, 11 or 12). In such cases you can use the right arrow to navigate to the next field - the day in the demo(see video attached, I'm only using keyboard navigation, no mouse).

In terms of the issue you are facing with fast typing, it is most likely due to high network latency. I have tested it locally but the issue is not present. You can also test it locally to see for yourself. In the meantime, you may find this article helpful to also test your network latency.

You might take into consideration that the necessary latency value for best performance may vary depending on the user action - for example, a button click is a typically slower action than typing and will work fine even with higher latency. On the other hand, fast typing will require much lower latency value in order for the application to perform as expected.

When working with online applications, Server side Blazor might not be the best solution in certain cases - for example if the user is far away from the server or if they are using a VPN, firewall etc, the application will not deliver the best results. Therefore, it might be a good thing to consider switching to the WASM version of Blazor. Since the WASM Blazor application runs directly in the browser, this reduces the necessity of a constant connection with the server and thus providing faster online performance.

As for the users nationality and date formats, you might go for localizing your application - more information how to achieve that you can find in our Localization docs article.

Regarding the "pressing 0  in the DateInput deletes the date" bug - since we have a bug report already opened for it, I will mark this one as duplicate in order to keep the portal clean and properly keep track of the requests. You can follow the original post to be notified on a status change.

Note: As per our feedback portal status scheme, the "Unplanned" status indicates that this is a valid bug report not scheduled for implementation yet.

Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Posted on: 08 Jan 2021 06:32
Further to this, note for non-US users, the date format must be: "d/M/yyyy". 'dd or mm' in non-US order will not work (for me anyway).