Requesting the addition of the OrgChart component to Kendo Vue (it's currently available for Kendo UI and React).

Add HTMLElement autofocus property support for input components like Input, Textbox etc...  See https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/autofocus

Currently, unable to apply autofocus as an attribute to Input (separately or as part of a Form).

 

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.
   

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.

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.

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 Kendo UI team,

I’m using the HeaderSelectionCheckbox feature in the Grid to let users select all rows and perform a bulk action (like deleting all selected items). This works perfectly, but I’ve run into a small UX issue.

After I programmatically remove all selected items (e.g., after a successful delete operation), the HeaderSelectionCheckbox remains in a selected state — even though there are no more selected or visible rows in the Grid.

Use case:
- User clicks the header checkbox to select all rows.
- User clicks "Delete", which removes all selected rows programmatically.
- The HeaderSelectionCheckbox remains selected, despite no rows being selected.

Question:
Is there currently a supported way to control the state of the HeaderSelectionCheckbox from user-land (e.g., via a prop or method)?
If not, would it be possible to expose an API or prop to manually reset its state?

Thanks in advance!

When enabling the columnMenu feature in the Grid component, it is also applied to special columns such as the group indicator column or the expand/collapse column. These columns are not user-defined and should not include the column menu.

This leads to a confusing UX where users can click the column menu icon on non-data columns, which serve internal purposes only.

Example: https://stackblitz.com/edit/uj5myrrw?file=src%2Fmain.vue

Expected behavior: Only user-defined data columns should render the column menu icon. Internal columns (like group indicators or row expanders) should not display it.

Hey!

When using the GridColumnMenuCheckboxFilter with large datasets (e.g. 100k+ items), the component performs poorly and can even crash the browser due to the lack of memoization and unnecessary recomputation.

There are two main optimizations that could drastically improve performance:

1. Simplify the data before passing it to the filter
Instead of sending the entire Grid dataset to the GridColumnMenuCheckboxFilter, it’s better to extract and send only the distinct values relevant to that specific column. This significantly reduces render time both for the menu and the grid.

2. Memoize the computation internally
If simplifying data externally isn't possible, the component should at least memoize the list of unique values it derives from the data. Right now, it recomputes this on every render, which is inefficient.

Example: https://stackblitz.com/edit/de8qtiht?file=src%2Fmain.vue

The example provides two ColumnMenu implementations:
    •    The default (unoptimized)
    •    A custom, memoized version with basic optimizations (memo + uniquify)

You can switch between them in main.vue to observe the performance difference.

Expected behavior:
The default GridColumnMenuCheckboxFilter should:
    •    Either memoize its internal computation (option 2),
    •    Or documentation should clearly recommend preprocessing the data before passing it in (option 1).

This change would vastly improve UX for users working with large datasets.