I would like the following behavior in the date picker. Perhaps it can be achieved with a parameter similar to the one in UI for ASP.NET AJAX - the FocusedDate property (something like RadDatePicker1.FocusedDate = DateTime.Today.AddDays(30);).

The current behaviour is:

* if date is set, show month of set date
*else show month of current date (today)

Desired behaviour:

* if date is set, show month of set date
* else if min date's month is greater than current date month then show month of min date
* else show month of current date

Here is a code snippet to illustrate the issue:

Open the picker - it will start in the month with today's date, but I want it to start at the min date - one month later

<TelerikDatePicker @bind-Value="@theDate" Min="@minDate" Max="@maxDate"></TelerikDatePicker>
@code {
    DateTime theDate = DateTime.Now;
    DateTime minDate = DateTime.Now.AddDays(60);
    DateTime maxDate = DateTime.Now.AddDays(230);
}

• When a user wants to clear a date a lot of time they will click at the end of the component and start hitting back space.  However, after the year is cleared at the end if you keep clicking back space it does not continue to also clear the month and so on.
• I'd like an option that allows free form typing and it does not parse as you type.  It just allows you to enter the text input like if it were a regular text box.  When you click enter or drop out of focus then it will parse the value as appropriate to what the user enters in.  This would be an example: https://www.matblazor.com/DatePicker .   The user could type in whatever format they want and then it'll parse it into the format that I've selected.  They could enter 2023-07-06, 07.06.2023  04/06/1983 4/6/1983 4/6/83 and it would parse as appropriate and the set the value as appropriate.
• When you single click into a date picker text box it will highlight the closest date part.  However, if I then try to click again to select the entire date, where the user is just trying to copy and paste it'll do this weird dragging of the highlighted date portion with a do not enter icon.  I would expect that it would allow you to continue selecting the entire contents of the text box so I can then copy and paste.
• If I only focus on for example the first character of the text box and then try to paste in a value from another form it does not take the copy and paste.  I would honestly expect that copy and paste regardless of what individual element that you are focused on what accept the new value that I am trying to paste.  If I paste in 07/06/2023 anywhere in the text box it should parse that and replace the entire date like if I selected the entire contents of the date and pasted it in.  The free form typing would resolve the useability issues here though.
• For time picker I'd like some different UI options.  The existing implementation is ok, but if we had options to format the the timer picker like: https://mudblazor.com/components/timepicker#api or other times if we want to lock them in to only specific time intervals it's better to just have them select a time from a drop down.  I realize that the drop down method could be implemented in other ways but if it was just baked into the control it would be a lot easier.

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

Ideas that would serve me:

• spinners like those of the time pickers
• simple dropdowns like here
• ux like here

When using an abbreviated month in the date format, the picker will not automatically move to the next element (year) after entering a month. If I enter 04 for example, the focus remains on the month.

When using a numeric month in the date format, the picker will automatically move to the year after entering a month.

See an example: https://blazorrepl.telerik.com/cmOzPgFc08d1woml09.

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.

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.

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.

When testing your datepicker control in NVDA, there are a number of accessibility issues.

1. The dateinput portion of the control does not account for users entering full dates into the control, meaning if a person was to try to type 2/23/2022 into the input where they included the slashes, it would throw them into the year section when they thought they were entering the day section.  My suggestion via this forum link (https://www.telerik.com/forums/ignore-forward-slash-allow-various-formats-when-using-date-input) is to alter your date entry logic to allow users to both enter the dates without the slashes (which is what you have now except under a few edge cases where a slash is needed to move to the next section like 2 2/ 2022) as well as include the slashes where if the user is on the first digit of the day section and the / is pressed, do NOT advance them to the year section.  While this can be an annoyance for a sited user because they end up accidentally entering the day in the year section when they try to use the slashes, they can at least see what went wrong, and then go back and fix it. For a screen reader user, they are not notified of the auto advancement, and so they have no idea that they have entered an invalid date until the leave the control and then tab back to it, or if they were to try to submit the form and get an error.
2. The dropdown portion of the control is not being read properly by NVDA.  When you first drop it down via alt-down arrow, it will actually write all of the table text to the Speech Viewer window, but nothing is read. 
3. Then, once you try to arrow to a date, nothing is read at all. You can tab to the month and previous/next buttons and they are read.
4. Opening the Month section of the dropdown doesn't read the month out when arrowing through the months.
5. Tabbing to the previous or next buttons and then pressing them with enter reads all of the dates in the table.
6. Arrowing up or down within the days reads all of the dates in the table when it advances to a new month, but reads nothing otherwise.

I am using the latest version of NVDA 2021.3.3 on Chrome Version 98.0.4758.82 (Official Build) (64-bit).  I will note that Jaws and Chrome work properly regarding the dropdown issues, so it may be an NVDA thing, but maybe some research can be done to see if there are some different aria attributes that will work so that if functions properly with both screen readers.  For example this Aria Best Practices Date Combo Box example at least reads where the user is with the arrow keys. https://www.w3.org/TR/wai-aria-practices-1.2/examples/combobox/combobox-datepicker.html It is not perfect, but it is better than not being read at all.

And even outside of the date dropdown stuff, the date input portion (#1) above is an issue across the board. I know that it is a design decision that you guys have made, and that you have provided documentation as to why and how to use it, but most users are going to type in the slashes of a date, and it's not reasonable to write up a half page of documentation within my app to let users know how to use the control.  I can't even put a short label that says enter date without slashes, because under some circumstances a slash is necessary, so it becomes confusing to the user, and screen reader users will get lost if they make a mistake because they are not informed that they have just switched to a different section.

Thanks.