when expanding a group, inside the expand event (function) we do have access to the groupIndex.

but groupIndex is not available inside the groupHeader(Footer)Template itself.

we need that groupIndex, so we can get the parent items (groups) to the group that is expanded.

When mouse hover over a specific row, a tooltip to show more information should be shown

disable grouping on a column

Please think about an implementation of toolbar template for grid, similar to the jQuery version.
Can we expect something like this in the near future?

Hi,

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

 

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.

Cheers,

Clint

I've created a Plunker: http://plnkr.co/edit/WoqkaDZpq8hU24m0eKcv?p=preview

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.

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:
https://www.telerik.com/kendo-angular-ui/components/grid/columns/menu/

Add events like detailInit, detailExpand, detailCollapse in the Kendo Grid for jQuery. Add possibility to know whether the detail template is expanded or not.

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.

Can you please consider adding a built-in option for freezing Grid rows that will always stay below the headers area during scrolling?

When using virtual scrolling and the data changes, then it might be desireable to programmatically scroll to top or to scroll to a row containing the data of interest.

"~@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.

I need to expand/collapse grid rows programmatically. I know about grid.expandRow/collapseRow, but there is no public methods which can get me know  is row expanded at this moment and collapse it. I need to manage in component array of expanded rowIndexes and every time to check is row expanded,then call method collapseRow, which again, under hood, using your private method this.detailsService.isExpanded(index), is doing this check. It's very inconvenient.  So, can you expose this methods or toggleRow() to allow us get rid of additional logic around? Or, possibly, you know other way to get this info directly from grid?

I want to display my data in multiple type of views (grid, listview ...etc). So I need to place PagerComponent outside of GridComponent

It would be nice to have support for horizontal virtual scrolling for the Grid in cases of large number of columns. Just like the current feature for vertical scrolling, in which you can update the visible rows through a pageChange() event handler.

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.

If the value "-1" is passed in as one of the values in pageSizes input for the PagerPageSizesComponent, that option should be shown as "All" and should show all rows available for the grid.

Scrolling like this : http://legacy.datatables.net/release-datatables/examples/basic_init/scroll_y_infinite.html

Say you have 100.000+ rows of data.
With classic or virtual scrolling, you allow your user to go to the last page very easily. It ends up with huge skip parameter, and disastrous load times from the DB.

You don't want users to be able to run queries which are at the same time useless and very time-consuming server-side.

What you really want is for your user to be able to browse a bit of the data with fast queries, and if he wants something else, he should filter data.

Infinite scrolling gives him just that feeling.

It would be great if grid component has option to filter date and numeric columns by range.