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
there is no way to set value in formatted input after blur and focus

To Reproduce
Steps to reproduce the behavior:

1. Opon this Stackbliz - https://stackblitz.com/edit/6fnerfrf-3hulsidf
2. Focus the first input and select all the content
3. Delete the content and click outside of it
4. Then click again in it and try to type 33.98

Expected behavior
You can type it

Screenshots
Immediately 3.00 is typed and the cursor is moved at the end

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
Paragraph / Font Size / Font family do not work

To Reproduce
https://www.telerik.com/kendo-vue-ui/components/editor/
Paragraph / Font Size / Font dropdowns do

Expected behavior
Paragraph / Font Size / Font dropdowns work correctly

Currently you can either set the position of a window by specifying the top or left positions on the screen.  However once these are specified, the window is no longer draggable, or is only draggable in a specific direction, for example, set the :top="100" attribute on a window and the window is now locked to that height (100px) and can only be dragged left or right, instead of vertically and horizontally.

Please allow a window to be set to any position on the screen programatically at any time, and then allow it to be draggable if the draggable property is set to true.  A use case would be where a window is opened up next to another element on the screen, the user moves the window to get access to any underlying content and then closes the window.  It would be ideal to be able to programmatically specify where to open the window when the same method is called again.

Thanks.

I want to use filterGroupByField to indicate that a column that has a GridColumnMenuCheckboxFilter.  Naturally, there can be more than 2 items selected.  If more than 2 items are selected, the filterGroupByField returns null.

See this example (select more than 2 product id's):

https://stackblitz.com/edit/i58xwv?file=src/main.vue

@open and @close events are not triggered by integration testing tool, even when programmatically calling the event.

We are using cypress 11.1.0

cypress-real-events: 1.7.4 was also used to try of trigger the events but didn't work.

The way we try this was by:

cy.get(element).trigger(‘mouseover’)
cy.get(element).realHover()
cy.get(element).trigger(‘mouseover’)
cy.get(element).trigger(‘mouseenter’)
cy.get(element).then(el => {
    el.dispatchEvent(new MouseEvent(‘mouseenter’, { bubbles:true })
}

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

Add active class to the column menu icon once something in it is different from default

Currently we recommend using custom class on the header(https://www.telerik.com/kendo-vue-ui/components/grid/columns/column-menu/#toc-styling-the-column-menu-icon), yet not visualising that the menu is populated seems like a UI misleading issue when using the component so we should add it by default

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

The Upload component has the option to configure it to accept single or multiple files for upload. 

When the component is configured to accept only one file, the text in its Select button should be in singular form - "Select file..." instead of "Select files..."

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!