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.

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.

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!

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.

Can you please provide a native Vue Wizard Control like the JQuery one:

Demo of core features in jQuery Wizard widget | Kendo UI for jQuery (telerik.com)

Currently, the Kendo UI for Vue suite has only a Scheduler Wrapper component.

It would be nice if we can see a native version of the component.

Describe the bug
By default, the Dialog component is a modal window. This means that once the Dialog appears, the page elements are the only ones the users can interact with.

Currently, if you use the keyboard navigation functionality of the Dialog, after pressing the Tab key multiple time, the focus will be on the "Open dialog" button below the modal. This should not happen.

To Reproduce

1. Open this StackBlitz example
2. Click on the "Open in new window" button to open the example in a separate window/tab
3. In the new window, click on the "Open dialog" button
4. Once the Dialog is opened, press the Tab button 8 times and press Enter
5. The Dialog will be closed because, after the 8th Enter press, the focus will be again on the "Open dialog" button below the modal area.

Expected behavior
When using the keyboard navigation of the Dialog component, the focus shouldn't be transferred to the elements below the modal area. It should be kept among the elements that are displayed in the Dialog.

Greetings,

I hope this message finds you well.

I would like to request a new feature for the Kendo Vue Dropdown List component: the ability to disable selected items directly within the dropdown list configuration. This functionality is already available for Kendo React users, as outlined in your documentation:
Disabled Items in Kendo React DropdownList.

Why This Feature is Valuable for Kendo Vue Users

1. Consistency Across Frameworks
   Many users work across multiple frameworks, including React and Vue. Consistency in feature availability ensures a seamless transition and experience for developers leveraging Kendo UI in different projects.

2. Improved User Experience
   Disabling items within the dropdown is a common requirement in dynamic forms and data-driven applications. For example, when users are selecting items from a list, disabling already-selected options prevents confusion and enhances usability by guiding them effectively.

3. Reduced Development Overhead
   While developers can currently implement this feature manually in Vue, a built-in option would significantly reduce the amount of custom code required. This aligns with the Kendo philosophy of providing robust, ready-to-use components that save time and effort.

4. Enhanced Accessibility
   A built-in disabled item option ensures proper handling of accessibility concerns, such as ARIA attributes, keyboard navigation, and screen reader compatibility. This would help developers create inclusive and accessible applications without requiring additional customizations.

5. Competitive Edge
   Offering this functionality natively in Kendo Vue would strengthen the feature parity between your React and Vue libraries, making Kendo UI even more appealing to developers evaluating dropdown components across frameworks.

Proposal

Introduce a configuration option, similar to the one in Kendo React, that allows users to disable specific items in the Vue Dropdown List component. This feature could be implemented by providing a function or property to dynamically determine which items should be disabled based on their state or other criteria.

Please add Vue wrappers for Kendo Drag and Drop functionality.

Do you have a development plan?

Steps to reproduce:

(latest version of vue, vue CLI, node etc. installed globally)

• vue create test-project
• cd test-project
• npm install --save @progress/kendo-ui
• npm install --save @progress/kendo-theme-default
• npm install --save @progress/kendo-dateinputs-vue-wrapper
• added Calendar component to App.vue (see https://www.telerik.com/kendo-vue-ui/getting-started/)
• changed the name "kendo-calendar" in HTML template to "Calendar", otherwise I get build errors
• npm run serve --> browse to localhost:8080 --> error in console:

Uncaught ReferenceError: $ is not defined
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:85)
    at Object.eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:292)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:74)
    at Object.1472 (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:75)
    at __webpack_require__ (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:21)
    at Object.0 (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:49)
    at __webpack_require__ (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:21)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:41)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:44)
    at Object../node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js (app.js:3624)

I could reproduce the error using different Kendo UI for vue components like Buttons etc. (following the getting-started page for the button component). The default vue project template uses Babel and Webpack. Is there a configuration missing for Kendo UI?

I already checked:

• https://www.telerik.com/kendo-vue-ui/getting-started/
• https://www.telerik.com/support/whats-new/kendo-ui?utm_medium=internal&utm_source=yellowribbon&utm_campaign=kendo-ui-vue-awareness-r22019release#vue-updates-in-r2-2019
• https://www.telerik.com/blogs/what-you-need-to-know-about-vue-cli-3
• https://www.telerik.com/blogs/better-tooling-with-the-new-vue-cli
• https://www.telerik.com/blogs/integrating-vue-cli-3-with-kendo-ui
• https://www.telerik.com/blogs/creating-and-managing-vue-projects-with-vue-ui

Hi. 

I am looking for a Badge component in the Kendo UI for Vue suite. The component is available for the Angular suite(https://www.telerik.com/kendo-angular-ui/components/indicators/badge/) but not for Vue.

It will be nice to have this component available also for Vue.

Currently, Kendo UI for Vue suite provides export to Excel through the kendo-vue-excel-export package. The Excel export is a nice feature but the CSV export is another functionality that is often used.