A dedicated column picker would be far more intuitive: its discoverability is higher, and features like the indeterminate ‘select all’ checkbox and instant search align with the law of approximation.

For our users handling large datasets, this makes for a much faster, more cohesive tool.

1. You have documentation, eg at https://www.telerik.com/kendo-vue-ui/components/charts/sparkline

2. Type "sparkline" into the search box on your own website

3. No results are returned.

This used to work. You pushed a change which broke your site's search functionality.

Describe the bug
The rowReorder event is missing in the Wrapper Grid component, while it is available in the Kendo UI for jQuery Grid. Currently, the only way the event can be used is by using a code like the below in the mounted hook of the Vue app:

    var grid = this.$refs.grid.kendoWidget();
    grid.bind('rowReorder', function (e) {
      console.log('row', e);
    });

Expected behavior
The rowReorder event should be available for usage as the other events of the Wrapper Grid

Currently in Vue we don't provide the ability to share with the customers the source code before the compilation but just the already compiled code.

We need to provide the ability to fork the repository and build components from the Vue repository similarly to the way it is done in Angular and React. 

I am using Kendo Vue Wrapper Grid that is editable. I am using the propery 

:editable-create-at="bottom"

but the new rows are always added at the top.

There is another open issue related to this.

https://github.com/telerik/kendo-ui-core/issues/5198

Please provide a fix.

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
A licensing warning may continue to appear in the browser's console, no matter whether the licensing activation has been successful or not.

The issue is replicable when the user trying to activate a license has had an active license in the past and this license is already expired.

To Reproduce
Because of the specifics of the issue, a project in which the bug can be replicated won't be publicly provided.

Expected behavior
The license activation process should activate one's license no matter the previous licensing history of the user

Hello everyone

We are using Editor for our application,
Is it possible to add the possibility to Copy and Apply Format
It used to be included in the older version "@progress/kendo-editor-vue-wrapper"
Here a screenshot of the older one : 

Best Regards

It would be beneficial to explicitly control the left-to-right rendering order of overlapping events — for example, by using a custom field such as isPrivate or by following the data source order.

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.

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.

We have a requirement for the Grid to support sticky rows when virtual scrolling is enabled. I know it is documented as a known limitation on https://www.telerik.com/kendo-vue-ui/components/grid/rows#known-limitations but we would like to request the grid add this feature. We would also like to request this feature using grouped data, as I see it also is not supported in this scenario. 

One specific scenario is we have 2 groups and both groupings are sticky. The first group would have a few rows of data, while the second group has hundred or thousands of rows. We would like to allow for row virtualization on the second group while keeping the first group sticky at the top. Below is an example screenshot where we have the first "Benchmark" group having one row, the second "Investments" group having a sticky "Total" row at the top, and then rows of data that can be rendered with row virtualization to paginate.