Hi Kendo.

We're trying to replace Vue Grid Wrapper with the new Native Grid and most things works awesome. We only have one blocking feature that isn't inplemented yet.

So my question is when is the footer-logics comming for the native grid. We want to show aggregates in the fixed footer and it would be awesome it is like the 'headerCellRender' function defined on the grid. We know there is a gouping aggregate, but this isn't the thing we want.

Is there any idea when or even if it is comming to the native grid?

Kind regards,

Sander

Currently, the MulltiView configuration of the Calendar component doesn't visualize the months above each Calendar.

The requested functionality can be observed in this example from the Kendo UI for jQuery suite. The usage of the MultiView functionality of the Calendar will be easier if it looks similar to the linked above example. 

Hi Team,

Can you consider the implementation of a Native TileLayout component? 

It will be a very nice add-on to the Native Vue suite.

Hello there,

I am looking for a loading spinner solution to use with Vue Native Grid. I could not find something on the docs.

Is there any way I can show some kind of loading indicator while loading the data?

I am not using data source from Kendo, just basic method to populate `:data-items="items"`

Thank you!

For Vue components, the v-model on a multi-combo box and every component must bind to the underlying object.
:value-primitive="false" doesn't work as per some suggestions.

v-model binding to the underlying object is a MUST HAVE, Top priority, number one with a bullet. Without it, your components are a PITA to use and my current proof of concept might end here and we won't use your components with some bigger projects coming down the line.

I'm submitting a...

• Bug report

Current behavior

When the Date Inputs or DropDowns are positioned at the bottom of a page, their popup continues to open below the input field. This causes the popup to appear beyond the browser's boundaries, making the users unable to use the popup.

Expected behavior

The position of the popups of the Date inputs and DropDowns should be automatically changed based on the available space below each of the components. If there is not enough space to open the popup below the component's input, the popup should appear above the input.

Minimal reproduction of the problem with instructions

1. Open this StackBliz example
2. Click on the "Open in a New Window" button at the right corner
3. In the opened browser window, scroll to the bottom of the page
4. Open the popup of the DropDownList

The Spreadsheet component is among the last components in the Kendo UI for Vue suite that is available only as a Wrapper component. 

Providing a Native version of the Spreadsheet will be a big improvement to the suite. 

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!

Hi,

I'm interested in using Drawer for our project, but the current docs only seem to show that it's natively supported with jQuery. I know I can still use it on my Vue project with lots of jQuery usage, but I just wanted to confirm if Drawer is available or not with a vue wrapper to be able to continue with  my component more elegantly.

And if it does not exist yet, I would like to request a new feature for a Kendo UI Vue wrapper available for the Drawer module.

Cheers,

Mark

I'm submitting a...

• Bug report

Current behavior

When defining a custom cell template by defining a new Vue component few Vue warnings appear in the console. Here are the errors:

• [Vue warn]: Avoid mutating a prop directly since the value will be overwritten whenever the parent component re-renders. Instead, use a data or computed property based on the prop's value. Prop being mutated: "dataItem"
• [Vue warn]: $listeners is read-only.

Expected behavior

There should be any errors in the console when defining a cell template using a Vue component.

Minimal reproduction of the problem with instructions

1. Open this Dojo example
2. Sort the Grid by any column
3. See the browser's console

Environment

Package versions: kendo-vue-grid 0.3.7 loaded via CDN

I'm submitting a...

• Bug report

Current behavior

The user cannot select a filter operator if the filter input doesn't have entered data.

Expected behavior

The user should be able to pre-select a filter operator no matter if there is data entered in the filter input or not.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example
2. In the Product Name column, I click the filter operator button
3. Select "Ends with"
4. Click the filter operator button again and see that "Ends with" is not selected.
5. Type "g" in the filter text field. Grid updates but doesn't filter the data by "Ends with" filter.
6. Click the filter operator button and see that "Contains" is selected instead of "Ends with"
7. Select "Ends with" once more and Grid filters correctly

Currently, the Kendo UI for Vue Native DropDownList doesn't have the valuePrimitive property which is available in the:

• Angular DropDownList - https://www.telerik.com/kendo-angular-ui/components/dropdowns/api/DropDownListComponent/#toc-valueprimitive 
• and the jQuery DropDownList - https://docs.telerik.com/kendo-ui/api/javascript/ui/dropdownlist/configuration/valueprimitive 

Providing such property for the Native Vue DropDownList will be useful in different use-case scenarios. 

With the current implementation of the Native Grid, if one needs to set a minimum width to a column that needs to add the implementation suggested in this Setting a Minimum Column Width example.

While the approach in the above example works as expected, the logic that needs to be added can be internal for the Grid component. Thus the users will have to add a simple column property like the below and no other configuration should be set.

  {
    field: "ProductName",
    title: "Name",
    minWidth: 200
  }

Hello.

I want to request a feature for the Native Editor that is available in Microsoft Word.

I would like to be able to set the cursor on an existing hyperlink, click the Hyperlink tool, and change the display text on the hyperlink. 

This change would also include adding a "Display Text" form field on the hyperlink tool dialog view.

Describe the bug
The behavior of the Native and Wrapper MultiView calendars is different when using the next/previous arrows of the component.

The Native MultivVew calendar changes the selected date to the respective date of the next/prev month but doesn't change the month views as the Wrapper does.

Check the following two videos and see the differences:

To Reproduce

1. Open this StackBlitz project
2. Select a random date
3. Click on the "next" navigational arrow

Expected behavior
The same as the selected date should be focused on in the next month just like the Wrapper MultuView Calendar does.

Describe the bug
The Tooltip is not correctly positioned in scenarios where a longer text needs to be displayed. This incorrect positioning leads to the inability to automatically close the Tooltip when the mouse is hovered out of the component.

To Reproduce

1. Open this CodeSandbox example.
2. Hover the yellow dot on the right

Expected behavior
The Tooltip should appear correctly positioned above the yellow point as it is in the scenario when you hover the left point in the above example

Screenshots