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.
Currently the datePicker and probably other controls that implement the rangeValidation property do not listen to changes on the rangeValidation input.
This is preventing whether range validation is enabled based on other form input changes during user interaction with the form.
Can this be changed so it listens on ngChanges?
When both virtual scrolling and grouping are enabled via the kendoGridGroupBinding directive, and the Grid is
navigable, focus is trapped in the header row when down or up arrow is pressed:
Focus any content cell
Press up/down - focus goes to the header cell of the respective column and is trapped in the header row
On a feedback portal search and paging is not working.
Open feedback portal and enter search criteria with more then five item. example
When you want to view result for second page, search is not preserved (it is empty).
The example does not work:
I want to filter the scheduler data but I had to add the OwnerId property to the node package interface in order to be able to do so... yet the sample data provided in the examples does include the ownerId, so im guessing all that needs to be done is to add it to the interface.
When opening a dialog with DialogService from an Observable (e.g. in order to initialize dialog with data from a http request) and ChangeDetectionStrategy.OnPush, the dialog is messed up. With ChangeDetectionStrategy.Default everything works fine.
For reproduction have a look to this StackBlitz: https://angular-9vmvyv.stackblitz.io