The DatePicker and the rest of the picker that have the ShowClearButton parameter (e.g., TimePicker, DateTimePicker) do not hide the clear button, when the initial value is null or after the user clears the existing value. This is inconsistent with the TextBox behavior, or with the behavior of the pickers in other suites.
Workaround
https://blazorrepl.telerik.com/wpaiFzFc26Zot90s18
Run the following REPL example: https://blazorrepl.telerik.com/QfEWvzvc35O5poYW04
The clear button is visible.
If you select a date and clear it, the clear button remains visible.
The clear button is hidden.
All
No response
Changing the "day" part of the DatePicker value is inconsistent.
Run this example: https://blazorrepl.telerik.com/QfOLwTvp03DVHJ4C35
The value changes to: 20-02-2025.
After the initial unsuccessful attempt to change the day to 02, subsequent attempts will work as expected. You may re-focus the "day" part and type 02.
The value should change to 02-03-2025.
All
No response
We would like to get the datetime picker to autofill the year when entering just two digits for the year with a format of dd-MM-yyyy HH:mm:ss.
So when you enter 23-04-25 it changes to 23-04-2025. Currently it changes it to 23-04-0025, which isn't our desired result.
Something along the lines of how this works: https://jsfiddle.net/anbdwL0h/ but then with a 4 year digit format as result.
In our application "Today" is NEVER a valid selection. But there is no way to turn it off.
Yes, we realize that we can create our own header template. But then we have to reproduce the next/previous functionality, for every single instance of the component -- and we have many dozens of them.
When dragging the mouse to select the whole input value, only the first segment on the left remains selected after releasing the mouse. The issue is reproducible in the DatePicker demo once you select a date. Video: https://app.screencast.com/Eoa6Xj2MzfOPN.
The problem is only reproducible in Firefox, the whole input is properly selected in Chrome and Edge.
When the user navigates between the views, the DatePicker currently fires a ViewChanged event. This event provides the new view (Decade, Month etc.) but there is no way to detect the selection that the user made in the previous view.
For example, if am in the Decate view, as soon as I select a year, the DatePicker will switch to Month view. The problem that I am facing is that I cannot get the year selected from the Decade view. I need that, so I can display it in my custom HeaderTemplate.
For some reason I'm unable to select the date 01/03/2000 when using the date picker to select the date. Only thing special about this date is its exactly 24 years ago today.
I was able to reproduce in repl. https://blazorrepl.telerik.com/QyYFkdbU34QbG0Te32
I also attached a video so you can review the steps followed and result.
Currently, if the ReadOnly parameter value is set to 'true,' the user can modify the value of the DateInput by using the arrow keys.
Reproduction: https://blazorrepl.telerik.com/mxaiabvd178zy7p948
I have set both the Format and FormatPlaceholder. When I programmatically set the @bind-Value to null the Format is rendered.
I would like the FormatPlaceholder to take effect instead of the Format.
When attempting to insert a date of February 29th (2/29) in the DatePicker component with the AutoCorrectParts feature disabled, users are unable to input the year. The component only allows the insertion of the digits 0, 4, and 8, preventing users from selecting other year values.
Reproduction: https://blazorrepl.telerik.com/mxagmaPm39IQbjHw19
DatePicker cursor not advancing after month input. The problem arises when dd/MMM/yyyy format is applied.
To reproduce the issue open this REPL example. Type any date in the second DatePicker. When inserting a month value the cursor is not moved to the year section.
After inserting a month the cursor should be moved to the year section. As when no format is applied (the first DatePicker)====
Hi
I have created a REPL here: https://blazorrepl.telerik.com/QHYGbTPk59IqOcEU51
to reproduce the issue I am talking about:
you will notice that the value displayed below the table is what was previously in the cell
I would have expected the value to be null which can be achieved via