Hi,

I am requesting the option to disable parts of the navigation or the entire keyboard navigation in the AutoComplete component. The default setting for the Escape key is resetting the component and I am handling the Escape keydown globally in my application, that is why I need the option to disable it.

Thank you in advance!

It would be great to have column highlighting in the Grid, so when a user hovers over a cell, the entire column, including the header, is highlighted. Something similar to the example below, but built-in, would provide a better experience for both users and developers.

https://stackblitz.com/edit/angular-ink98nn6?file=src%2Fapp%2Fapp.component.ts

Please expose a moreEventsClick (or similar) event in the Angular Scheduler MonthView, triggered when users click on the "more events" indicator (three dots) that appears when a day has more events than can be displayed inline.

This feature exists in the jQuery version of the Scheduler and is extremely useful for navigating users to a more detailed view (e.g., Day or Agenda view) when event overflow occurs.

Suggested API:

(kendoMoreEventsClick)="onMoreEventsClick($event)"

Where $event includes:

{
  date: Date;
  events: SchedulerEvent[];
}

Use Case:

This allows developers to programmatically change the selectedViewIndex and selectedDate (e.g., show the Agenda or Day view for that specific date), providing a more intuitive user experience and consistent behavior across Kendo UI platforms.

Why it matters:

• Users expect the "more events" indicator to be interactive

• Enhances UX in event-heavy applications

• Aligns Angular functionality with existing jQuery features

Currently the more button goes directly to the Day view, our users do not like the day view and would like to go to the Agenda view!

Please add the following features to the Editor in Kendo UI for Angular 2+:

- Table Wizard

- Split cell row

- Split cell column

- Merge cell row

- Merge cell column

Note: These features exist i the Kendo UI for ASP.NET MVC version of the editor.

Currently, the pageSizes option of the available Grid's PagerSettings only allows passing a boolean or a number array as possible values. Thus, at the moment, the Grid component allows displaying an "All" option in the pager by implementing a kendoPagerTemplate:

• https://www.telerik.com/kendo-angular-ui/components/knowledge-base/grid-pager-all-option 

It would be great if an "All" page size option could be set directly through the settings of the pageable property by having the ability to pass a PageSizeItem array to the pageSizes option, similarly to how its done in the standalone Pager component:

• https://www.telerik.com/kendo-angular-ui/components/pager/api/pagercomponent#pagesizevalues.

Issue 1: Flickering or Not Opening of Dropdown

• Steps to Reproduce:
  1. Click on the color picker.
  2. Click on any dropdown.
  3. Observe the behavior of the dropdown.

Issue 2: Clicking on Color Picker and Dropdowns (Dropdown not closing)

• Steps to Reproduce:
  1. Click on the color picker.
  2. Click on any dropdown.
  3. Repeat this with all dropdowns to get above screenshot.

Currently, it is not possible to define a static pane in the Splitter with a fixed size that does not change when interacting with the surrounding panes, unless it is configured as non-resizable. In turn, configuring a pane as non-resizable affects the resizing ability of the surrounding panes as well, which means that they also become non-resizable.

It would be great if the Splitter could provide the ability to configure a static pane with a fixed size that is not affected by other functionalities like resizing, and in turn, have the possibility to resize the surrounding panes of a non-resizable pane.

Hi,

Recently I have implemented the date range component like described here: https://www.telerik.com/kendo-angular-ui/components/dateinputs/daterange/popup. The component normaly works as following: 

• A user selects the start or end datepicker and the calendar will open.
• The start of the range now needs to be selected.
• Then the end of the range needs to be selected.
• If a user would now select another date then this will be set as the start of the range.
• ....

But what a few users have issues with is the following scenario:

• User selects the start of the range.
• User selects the end of the range.
• User wants to change the end of the range so they select the same start of the range again and now select a new end range.
• As a result the start of the range is changed instead of the end of the range, because the click on the same start of the range didn't do anything.

The same issue also occurs with the MultiViewCalendar. I didn't add a runnable project because the same issue also occurs in the documentation which I linked above.

We are using @progress/kendo-angular-dateinputs": "17.0.1"

It looks like this line in the performRangeSelection method in the MultiViewCalendarComponent causes this behaviour:

const emitValueChange = (this.activeRangeEnd === 'start' && this.value?.start?.getTime() !== date?.getTime()) ||
            (this.activeRangeEnd === 'end' && this.value?.end?.getTime() !== date?.getTime());

Thanks,

Joren

The date range picker is not closing when tabbing through inputs when the picker is appended to the 'component'. It also seems that once the date range picker loses focus, it does not close by clicking anywhere else in the document until it regains focus again or the document loses focus.

I reproduced it in Stackblitz and attached a video. In the video there is a button after the date picker that logs to the console when it gains focus. Focus starts at the top of the document, start tabbing until the date range picker pops up, then continue tabbing through the date range picker until the button below the picker gains focus. As you can see the date range picker does not close. Here is the Stackblitz editor link to this: https://stackblitz.com/edit/kendo-daterange-bug?file=app/app.component.ts

Thanks!

Mitchell

Hi,

It will be a good component enhancement if selection and multi selection was introduced to the ListBox component. Like Kendo UI for React and jQuery:

https://www.telerik.com/kendo-react-ui/components/listbox/selection/

https://docs.telerik.com/kendo-ui/api/javascript/ui/listbox/configuration/selectable

Thank you for your consideration.

It would be great if we could add footnotes in the Kendo editor, similar to how TinyMCE handles them, or a simpler version like the example found here: https://prosemirror.net/examples/footnote/

Hi, Team!

I would like to request a functionality that allows users to navigate the slots inside the Scheduler (not just the events) using specific keyboard shortcuts.

Hi, Team!

I would like to request the addition of a functionality that would allow me to programmatically determine whether the cells for the weekends will be rendered inside the Gantt component!

This feature seems to exist in Kendo UI for jQuery: https://docs.telerik.com/kendo-ui/api/javascript/ui/gantt/configuration/showworkdays

When the values of the min and max properties of a Splitter pane contain both percentage and pixel values, there are cases when the values contradict with each other in different screen sizes. 

For example, if a Splitter pane's min is set to 100px and the max property is set to 20%, in certain screen sizes, the maximum 20% space that the Splitter should occupy may be smaller than 100px. 

It will be great if the Splitter can be enhanced with the ability to define which property should take priority over the other in order to handle such scenarios. 

It will be a good addition to the component if a placeholder option is provided for the filter input.

Current workaround - https://stackblitz.com/edit/angular-vcm2tlxf

Hello,

Please repeat the following steps to reproduce this issue:

The Grid provides column spanning by default, but the change is applied to all rows:

https://www.telerik.com/kendo-angular-ui/components/grid/columns/spanned

A good addition to the Grid would be to provide conditional columns spanning where some rows are normal while others - have spanned columns such as: