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. 

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?

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

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.

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.