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?

Describe the bug

After inserting an image using the "Insert Image" tool it is possible to add a hyperlink to it using the "Insert Hyperlink" tool.

If the image's dimensions are then edited by selecting the image and using the "Insert Image" tool, the hyperlink that was added no longer exists.

Before:

After:

To Reproduce

1. Open https://codesandbox.io/s/elegant-parm-l7w93g
2. Right click the image in the editor, you should see the option to open the link.
3. Select the image
4. Open the "Insert Image" tool
5. Change the width or height to another value (e.g. width -> 200px)
6. Click the insert button within the tool
7. Right click the image in the editor, you should see the option to open the link is no longer there.

Expected behaviour

The image should retain any hyperlinks that have been added even if it is resized.

Describe the bug
The following warning appears when using the InsertTable tool of the Native Editor:

[Vue warn]: Component emitted event "tableinsert" but it is neither declared in the emits option nor as an "onTableinsert" prop

NOTE: The warning won't appear when the project is built for production but, still this issue should be fixed

To Reproduce

1. Open this StackBlitz example
2. Insert a random table using the InsertTable tool
3. Check the browser's console

Expected behavior
No warnings should appear when using the InsertTable tool

Screenshots

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

Make the previous/next buttons of multi-day events functional like in the Telerik UI for ASP.NET AJAX control:

https://demos.telerik.com/aspnet-ajax/scheduler/examples/day-week-multi-day-views/defaultcs.aspx 

Describe the bug
The color of the Gauge component is not reactively updated when the value passed to its pointerColor prop is updated.

To Reproduce

1. Open this StackBlitz example
2. Change the selection in the radio buttons

Expected behavior
The color of the Gauge's pointer should be changed every time the selection in the radio buttons is changed

Screenshots
Red pointer:

Green pointer:

Add Adaptive Slot Height functionality for TimeLine view like the one available for Month view:

https://www.telerik.com/kendo-vue-ui/components/scheduler/adaptive-slot-height 

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

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

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.

Hi, Team. 

With the current implementation of the TreeList, if there is a vertical scrollbar in the component, this scrollbar starts from the header cells.

Can you consider making the scrollbar top position start below the header cells of the TreeList? As a reference, you can use the behavior of the vertical scrollbar in the Grid.  

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!