When starting he component, to load the initial value, the Api returns the id selected as a string ("2") and DropDownList does not display the selected option. Changing the value to an integer (2) displays it correctly.

This issues requires changing the values before padding them to component, but I would  that the component parse automatically the comparision, or allow us handle the strict comparision

Make the previous/next buttons of multi-day events functional like in the Telerik UI for ASP.NET AJAX control:

https://demos.telerik.com/aspnet-ajax/scheduler/examples/day-week-multi-day-views/defaultcs.aspx 

Add Adaptive Slot Height functionality for TimeLine view like the one available for Month view:

https://www.telerik.com/kendo-vue-ui/components/scheduler/adaptive-slot-height 

Currently you can either set the position of a window by specifying the top or left positions on the screen.  However once these are specified, the window is no longer draggable, or is only draggable in a specific direction, for example, set the :top="100" attribute on a window and the window is now locked to that height (100px) and can only be dragged left or right, instead of vertically and horizontally.

Please allow a window to be set to any position on the screen programatically at any time, and then allow it to be draggable if the draggable property is set to true.  A use case would be where a window is opened up next to another element on the screen, the user moves the window to get access to any underlying content and then closes the window.  It would be ideal to be able to programmatically specify where to open the window when the same method is called again.

Thanks.

The Upload component has the option to configure it to accept single or multiple files for upload. 

When the component is configured to accept only one file, the text in its Select button should be in singular form - "Select file..." instead of "Select files..."

The axisRanges property of the zoom event when you zoom on a chart object is empty, It should contain the ranges of the axes in the zommed area.

Hi, Team. 

With the current implementation of the TreeList, if there is a vertical scrollbar in the component, this scrollbar starts from the header cells.

Can you consider making the scrollbar top position start below the header cells of the TreeList? As a reference, you can use the behavior of the vertical scrollbar in the Grid.  

I would like to suggest adding a seamless typing feature in the Kendo Vue DateInput component, enabling automatic navigation between each section (day, month, year, hour, minute) without requiring separators or manual navigation.

✳️ Expected Behavior:

When typing a date and/or time, such as 20/04/1997 14:35, the cursor should automatically move to the next segment when the expected number of digits is reached:

For dates:

• Typing 20 → cursor jumps to month.
• Typing 04 → cursor jumps to year.
• Typing 1997→ date completed.

For times:

• Typing 14 → cursor jumps to minutes.
• Typing 35 → time completed.

👉 User flow example:

20 -> (day filled, move to month)
04 -> (month filled, move to year)
1997 -> (year filled, move to hour)

14 -> (hour filled, move to minute)
35 -> (minute filled)

✅ This would apply to all DateInput modes:

• Date only.
• Time only.
• DateTime combined.

❌ Current Situation in Kendo Vue DateInput:

• Manual use of arrows or mouse to move between segments.
• Need to type separators (/, :, etc.) explicitly.
• No automatic focus jump when a section is completed.

✅ Requested Feature:

• A prop to enable/disable automatic segment navigation in DateInput.
• Applies to both date and time segments, depending on the configured format.

🛑 Why it matters:

• Faster and more fluid typing experience.
• Matches native behaviors found in <input type="date">or <input type="time">in many browsers.
• Important for data-heavy environments (administrative forms, back-office systems, repetitive entry).
• Accessibility-friendly: reduces the need for manual cursor manipulation.

⚙️ Additional context:

After discussing this with your team, I understand that this behavior is not currently planned and custom implementations are challenging to achieve.
Still, exposing this behavior as an optional prop would allow those who need this fluid UX to benefit from it, without affecting existing users.

Thank you very much for considering this suggestion!

When enabling the columnMenu of a Grid, it should be hidden by default on all expand type columns (when using grouping or detail row). It makes no sense for it to appear in the headers for these columns as the sorting and filtering functions do nothing.

I'm aware the columnMenu can be enabled on individual columns, rather than the entire Grid, but the menu should not appear for columns where it has no purpose.

I know this exists: https://www.telerik.com/kendo-vue-ui/components/knowledge-base/scheduler-highlight-today-date-in-all-views
This breaks my scheduler unfortunately. I don't really have time to create a stackblitz and follow it further. 

I think the slot with the current Date should have the class k-today out of the box.

It would be nice to have the same X option that is available in the ComboBox.

clearButton - https://www.telerik.com/kendo-vue-ui/components/dropdowns/api/comboboxprops#clearbutton

It would just set the DateTime to null.

I'd like an AM/PM option for:

https://www.telerik.com/kendo-vue-ui/components/dateinputs/api/dateinputcustomformatplaceholder

Hi Team,

In Grid, Using optical mouse When Moving left to right or vice versa I should be able to move the grid as happening for top to bottom. In the attached video I have first used optical mouse and then Next I have used from laptop(Not optical mouse). 

NOTE: When Mouse click and drag I must be able to drag from left to right or vice versa.

Kindly look at the behavior and let me know the solution for this issue.

I would like to be able to select elements in the tree using shift: click on element #1, then click with shift on element #20 - all elements from 1 to 20 are selected

I also want Ctrl + A to work - select all

In general, this is necessary for all grids, tables, etc.