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!

Based on the feature set of the current jQuery widget - http://demos.telerik.com/kendo-ui/diagram/index

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.

Limitation:

• Font size in Kendo Editor only supports PX (pixel) values. 
• To customize the font size to show in PT (point) format in Editor, manual conversion has to be done using the below formula. However, the font size is not exactly the same as Microsoft word PT measurement.
  • 1 Point [pt] =  ~ 1.33 Pixel [px] 

Feedback: Font size dropdown can be provided for PT (Point) option as well as to follow like the Microsoft Word font size.

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.

Provide an option to focus programmatically a multiselect item, in order to prevent the popup list from scrolling when the last item is selected.

Here is an example:

https://stackblitz.com/edit/angular-qpbow1-awhxbr?file=app%2Fapp.component.ts

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

Hi Team,

Currently, the zoom property is only responsible for setting the initial zoom level of the document inside the PDFViewer component. I would like to request an option that would allow setting the zoom property dynamically/programmatically.

Current behavior
The grid component already has the functionality to resize and reorder columns by the user, but is missing functionality for saving an restoring columns configuration, so that changes done by the user are lost after a page change.

There is the Persist the State article in the "How to section" in the documentation, but the described solution is only applicable when adding grid columns by using *ngFor. When defining columns in the markup, due to extensive usage of templates (kendoGridColumnMenuTemplate, kendoGridFilterMenuTemplate, kendoGridCellTemplate, ..), there is no reasonable solution available.

Expected behavior
Provide methods, similar to the jQuery grid, to save and restore columns configuration. This should at least include the column's order, width and sort.

PS: This is not a duplicate of the feature request Add persistent state for grid (and other components). The latter one has been marked as "Completed" but does not include the needed functionality.

Hi,

Currently, the all-day events that last for more than 24 hours can be displayed only in the specific all-day row. Please provide an option that allows displaying the all-day events in the Scheduler main view as well. 

thanks

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,

It will be a good feature to have the ability to hide/remove the toolbar and footer toolbar of the Scheduler component.

Hi,

It will be a good addition to your standalone examples if a Java backend implementation is also added to the list:

https://github.com/telerik/kendo-angular/tree/master/examples-standalone

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.