It would be great if the Kendo UI for Vue had a MultiColumnCombox component

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.

It would be beneficial if the ChartTooltip exposed an appendTo, offset or collision prop.

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. 

Hello,

I’ve encountered an issue when using the KendoUI Grid component inside a dialog. When I try to open the column menu, it opens briefly and immediately closes itself, making it unusable.

This behavior seems to be related to a conflict with the UI component library I’m using (Ark UI). However, since the Grid’s source code is not open source, it’s difficult to pinpoint exactly where the issue originates or where a patch could be applied.

Reproduction:
Here is a minimal reproduction on StackBlitz: https://stackblitz.com/edit/rmldf7vs?file=src%2Fmain.vue

Expected Behavior:
When clicking the column menu button, the menu should remain open, allowing the user to interact with it.

Actual Behavior:
The column menu opens and instantly closes, without any interaction.

Notes:
- The issue only appears when the Grid is rendered inside a dialog.
- It might be related to focus/blur or click outside detection behavior conflicting between Kendo and Ark UI.
- Tested with the latest version of @progress/kendo-vue-grid.

Let me know if any additional details are needed!

Thanks!

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!

It would be great if the Kendo UI for Vue Native Grid had a built-in contextMenu similar to React

How to add grid footer (one row with one cell for all columns). When I try to use grid cell footer template I can't pass colspan to it (to normal cell I can). When I build template for normal cell it replace whole <td> section. When I do it same for cell footer the template content is placed inside predefined <td> - I can't replace it by my code like in normal cell. 

Can You add grid footer for all colums or fix footer cell template to work like regular cell template?

The Agenda view currently does not provide a way to customize the content of the Time column. For events that span multiple days (especially all-day events), this limitation makes it difficult to visually communicate when an event starts, continues, and ends

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

It would be great if there was an exposed prop for changing the filter operator of the ColumnMenu searchbox

It would be beneficial if we had a prop which allowed to fix the date header row in day view so that it does not scroll

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

The problem occurs only on a component DropdownTree in which the filtering fonctionality is enable.

I have this problem when testing on Chrome and Firefox.

Describe the bug
When working with the Wrapper DropDownList, if the component uses the v-model directive, there are some white spaces appearing in the popup of the component.

If the component doesn't use the v-model, the described behavior is not replicable.

To Reproduce

1. Open this StackBlitz example.
2. Select "Fish"
3. Select "Pizza"
4. Repeat steps 2 and 3 multiple times
5. See the white space in the popup

Expected behavior
No white space should appear in the popup of the DropDownList component.

Screenshots

Hello Team,

Icon for MS Word is missing the logo which is impacting UX for our application. Appreciate if this is resolved on priority

Reference in the Image: Docx 1. docx

Providing a Native PDFViewer Component to Vue would bring it in line with other UI platforms and provide a much needed feature for our use.

It would be beneficial if the Kendo UI for Vue had a Report Viewer similar to other suites