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.

Describe the bug
Paragraph / Font Size / Font family do not work

To Reproduce
https://www.telerik.com/kendo-vue-ui/components/editor/
Paragraph / Font Size / Font dropdowns do

Expected behavior
Paragraph / Font Size / Font dropdowns work correctly

Describe the bug
DropdownTree component throws an error when user opens dropdown menu when they selected an item already, if valueRender prop is configured.

To Reproduce
Steps to reproduce the behavior:

1. Open this example - https://codesandbox.io/p/sandbox/3tmtkk?file=%2Fsrc%2Fmain.vue
2. Select any item from DropdownTree. No errors would be thrown.
3. Try to press on dropdown tree to open dropdown menu again.
4. User will see this error instead of dropdown tree menu opening.
   

Describe the bug
If there is an event that ends at a specific time, it does not visually end at this specific time, but instead it looks like the event ends a few minutes earlier. For example, if an event ends in 2:30 AM, it is displayed like the end of the event is at 2:27 AM.

To Reproduce

1. Open this StackBlitz example
2. Scroll the Scheduler to the right until you see the 2:30 AM header
3. See that the two events are not aligned within the 2:30 AM boundaries

Expected behavior
When an event is set to end at a specific time, its visual representation should end at the line representing the specific time, and not before/after it.

Screenshots

Describe the bug
there is no way to set value in formatted input after blur and focus

To Reproduce
Steps to reproduce the behavior:

1. Opon this Stackbliz - https://stackblitz.com/edit/6fnerfrf-3hulsidf
2. Focus the first input and select all the content
3. Delete the content and click outside of it
4. Then click again in it and try to type 33.98

Expected behavior
You can type it

Screenshots
Immediately 3.00 is typed and the cursor is moved at the end

Describe the bug
When used in a Nuxt project, the DropDownButton component triggers the following console warning:

To Reproduce
Steps to reproduce the behavior:

1. Create a new Nuxt project following the instructions here.
2. In the app.vue file of the newly created project add the code from this example.
3. Add a Kendo Theme
4. Start the project and see the warning in the console

Expected behavior
The DropDownButton should now throw any warnings when used in a Nuxt project.

The data that reproduces the behavior is shown below.

https://stackblitz.com/edit/4d7wyn-buonwc?file=src%2Fmain.vue

The first value of the array data is shown below, but it may not match what is displayed on the graph or may not match other data such as the end.

I would like a fix or a feature that matches the data in the points plotted in the three vertical columns of the graph with the data in each array.

max_cell_volt: 4226
min_cell_volt: 3244
cell_volt_diffrence: 982

Hi Telerik Support,

how can I use Kendo vue MultiSelect with comma as selection instead of enter. if I press comma, it will select / enter the custom value. My case is I want to use it as email selection. on many email clients, it can use comma as email selection from the list or separation between values. How can I do this on MultiSelect vue ?

Thank you.

Greetings,

I hope this message finds you well.

I would like to request a new feature for the Kendo Vue Dropdown List component: the ability to disable selected items directly within the dropdown list configuration. This functionality is already available for Kendo React users, as outlined in your documentation:
Disabled Items in Kendo React DropdownList.

Why This Feature is Valuable for Kendo Vue Users

1. Consistency Across Frameworks
   Many users work across multiple frameworks, including React and Vue. Consistency in feature availability ensures a seamless transition and experience for developers leveraging Kendo UI in different projects.

2. Improved User Experience
   Disabling items within the dropdown is a common requirement in dynamic forms and data-driven applications. For example, when users are selecting items from a list, disabling already-selected options prevents confusion and enhances usability by guiding them effectively.

3. Reduced Development Overhead
   While developers can currently implement this feature manually in Vue, a built-in option would significantly reduce the amount of custom code required. This aligns with the Kendo philosophy of providing robust, ready-to-use components that save time and effort.

4. Enhanced Accessibility
   A built-in disabled item option ensures proper handling of accessibility concerns, such as ARIA attributes, keyboard navigation, and screen reader compatibility. This would help developers create inclusive and accessible applications without requiring additional customizations.

5. Competitive Edge
   Offering this functionality natively in Kendo Vue would strengthen the feature parity between your React and Vue libraries, making Kendo UI even more appealing to developers evaluating dropdown components across frameworks.

Proposal

Introduce a configuration option, similar to the one in Kendo React, that allows users to disable specific items in the Vue Dropdown List component. This feature could be implemented by providing a function or property to dynamically determine which items should be disabled based on their state or other criteria.