Last Updated: 26 May 2020 13:27 by ADMIN
Scheduled for 2020.3
Created by: Clint Singer
Comments: 1
Category: Grid
Type: Bug Report


It seems there is an issue with the material theme and nested grids.   When you have master-detail nested grids, the entire last nested grid gets applied with the same styling as the bottom rows of all the other nested grid. 

The styling in my browser is showing up as

.k-grid .k-grid-content tr:last-child td.k-grid .k-grid-content-locked tr:last-child td {
  1. border-bottom-width: 0;


Which causes the rows in the last grid to not appear.   

I have attached an image where I have changed the styling to 5px and red so you can see that it is being incorrectly styled.  You can see that even the other rows in in the last grid are getting styled along with the last row style.

I am running the latest version of Kendo.



Last Updated: 18 Mar 2020 07:20 by ADMIN
Created by: Troels
Comments: 3
Category: Grid
Type: Bug Report

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

Run the demo, press the "Open dialog" button a number of times, then take a heap snapshot in the Chrome dev console (be sure to first select the proper Javascript VM instance, containing "angular-thr9j1" or "angular-ksfrqy"). The component shown in the dialog is called "MemoryLeakDialogComponent", so use that as a filter. You'll see that for every time you opened the dialog there's now an instance of the component on the heap.

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.

Pending Review
Last Updated: 06 May 2019 07:16 by ADMIN
Created by: Merlin
Comments: 1
Category: Grid
Type: Bug Report

In Version 74.0.3729.108 (official Build) (64-Bit) of chrome, a defined grid with no predefined style property does not scroll properly. 

There is a live-demo on Stackblitz at https://stackblitz.com/edit/angular-b38r7s-jzsgty


This is a fork of the demo example from the kendo-angular-ui documentation available at


In the example, the scrollable grid was defined with a height property. This does not feet to our requirements, as we need a grid component that should flex according to the outside or parent container. 

This problem occured after the update of chrome browser from 73.0.XXX to the version 74.0.3729.108

The problem is fixed when we defined a grid with a height property like [style.height.%] = “100” but according to the documentation the grid should flex automatically without this property. 

Pending Review
Last Updated: 03 May 2019 11:14 by ADMIN

Use IE11:

1. Try to use the grids column menu for filtering

2. Click the column icon => popdown menu opens

3. Click the filter oder column icon inside the menu => nothing happens

I can't even open up your docs using IE11, it just loads forever: