Last Updated: 30 Nov 2021 09:28 by Alessandro

Hi, the following steps to reproduce the problem:

As you can see, the three dots menu of the not ticky columns are not hidden when overlapped by sticky columns.


Best regards,



Last Updated: 24 Sep 2021 05:54 by ADMIN

There is a bug with the kendoGridGroupBinding directive when changing the input data and using virtual scrolling.  If you have many rows and scroll down to a lower virtual page and then change the input data to a small subset the grid will think there is no data.  And if you then change back to the full data set you have to start scrolling down before the grid repaints with data.  

Reproduction available here


1. scroll down halfway in the grid

2. click the "Show subset" button.  Note the grid shows the no records message but should show three rows

3. click the "Show all" button.  Now the grid shows the scrollbar and the no records message is gone but it is not showing data.  You have to scroll down past where you previously were with all data before it repaints the rows

One workaround is to have an ngIf on the grid to destroy and recreate the grid when the input data changes, something like this:


  private destroyAndRecreateGrid(): void {
      tap(t => {


Last Updated: 13 Aug 2021 11:52 by ADMIN

Essentially the most basic GridComponent when ngIf'd in and out will not be collected -- apparently because of orientation change / resize change listeners not being appropriately removed.

Steps to Reproduce

Click the TOGGLE TABLE button to hide the table

Click the TOGGLE TABLE button to show the table

repeat several times

Take a memory snapshot

There will be HTMLTableRowElement items that grow each iteration of toggling the table.

The HTMLTableRowElements retention shows that they eventually lead to a resize listener, or an orientation change listener.

Last Updated: 24 Jun 2021 06:13 by ADMIN
Created by: Kendo UI
Comments: 0
Category: Grid
Type: Bug Report

When a Grid cell is focused, and after this, the data is filtered so that the data contains fewer items than the index of the row the last focused cell was in, the Grid table area does not receive focus when tabbed into.


Please check the example:


Last Updated: 16 Jun 2021 12:35 by ADMIN
Release 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: 15 Jun 2021 15:22 by ADMIN
I've created a Plunker:

Show the detail template of Row 1 in Beverages, then collapse the Beverages group. the Detail for Chai does not go away with the rest of the table.
Last Updated: 15 Jun 2021 09:01 by ADMIN
Created by: Chris
Comments: 3
Category: Grid
Type: Bug Report

When resizing grid columns so the last column does not reach the right border of the grid (sum of columns width < current grid width), loading stored state (or changing column width property in any way) does not restore the columns width proportionaly to use the full width of the grid.

Note: in this case, the default columns width sum and stored state columns width sum are always inferior to the grid width in order to use proportionality and adapt to every screen size.


In our implementation, we made a "Reset columns view" (working exactly as the loading store data), but if the user play arround with the columns as described above), the reset is broken.


Reproduce steps:

Using the persisting state exemple available in the doc:

- Click "Save current state"

- Resize grid columns so the last column does not reach the right border of the grid

- Click "Load saved state", the columns are resized proportionaly of the saved state but on the base of previous columns width sum instead of the full grid width.

Last Updated: 18 May 2021 15:47 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:

Last Updated: 13 Nov 2020 09:53 by ADMIN
"~@progress\kendo-theme-default\scss\utils\_float.scss" contains classes that the grid relies on (k-floatwrap, k-grid-toolbar), but "~@progress\kendo-theme-default\scss\grid\_index.scss" does not import it.  This requires me to explicitly import "~@progress\kendo-theme-default\scss\utils\_float.scss" myself.
Last Updated: 07 Jul 2020 07:22 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


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. 

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: and an Angular 9 demo here:

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.