Currently all text is wrapped inside a P tag, which is very inconvenient in many cases. Couple of examples:
Currently the Scheduler does not provide an opportunity for splitting very large datasets into portions via paging or virtual scrolling. This leads to decreased performance when a very large amount of resources needs to be rendered in the same view.
Please introduce virtual scrolling and/or built-in paging capabilities to resolve the performance issues.
Add Timeline Month View for Timelines like in jQuery
When the tabstrip have multiple tab within a limited width, the tabs are rendering outside the limit of the tab.
The component behavior should (perhaps by options configuration):
This can be reproduced using the StackBlitz of the tabstrip.
Provide an auto event height functionality in order to display the entire content of the event in the Moth view:
Provide the possibility to dynamically change the height of the slots in Month view, in order to fit the events in the specific slot:
As described here:
We are asking to add a simple css class to every master row opened. We have just to change stile every time row has detail open.
When using the Grid control inside an Angular component which is shown in a dialog (via MatDialog), the component is not properly destroyed after closing the dialog. The same problem doesn't occur when the component instead contains, say, a TreeView.
The problem occurs in Angular 8 and 9, in the Chrome browser. I've created an Angular 8 demo here: https://stackblitz.com/edit/angular-thr9j1 and an Angular 9 demo here: https://stackblitz.com/edit/angular-ksfrqy
The MemoryLeakDialogComponent contains just an empty kendo-grid tag with no attributes. If you edit its dialog template to instead contain a kendo-treeview component, everything is properly destroyed and garbage collected, which leads me to suspect a memory leak in the Grid component.
Please provide a feature like the following: https://demos.telerik.com/aspnet-ajax/scheduler/examples/creatingappointmentswithdraganddrop/defaultcs.aspx
Thanks and regards
Currently the grid uses indexes to memorize which data row is expanded. When a new row is inserted (due to a new data item inserted in the underlying collection) before a currently expanded details row, then then expanded details view will shift to the row before (old index). This is not desirable in a scenario with a lot of adding/removing of items. It would be great if memorizing expanded details row could be bound to the data object.