Next Release Target: TBD - 20.1.0 just released

******* For the time being, we've created a workaround which you can find in the following Plunker which uses a hard-coded refresh: https://next.plnkr.co/edit/peUBAixMVzg3KZfM ******

We did some analysis on this and determined we won't address this issue due to the complexity it introduces vs the benefit. A working solution would require us to detect which other rows need to be rendered in the DOM before we encounter them due when row spanning is enabled. A possible workaround for some users would be to set the rowBuffer to a sufficiently large number

Can be alleviated by using blockLoadDebounceMillis={x} https://next.plnkr.co/edit/KywppuQFnuAMNCo2

This is not an issue as you can conditionally obtain either the 'rowGroup' or 'rowUnGroup' items from the supplied defaultItems.

Changing the nature of this from bug to complex feature request. This will require a change in the architecture of the filters since the underlying model is always changed. It will get considered as part of filters revamping

Current workaround is to use a custom action on the context menu: https://ag-grid.zendesk.com/hc/en-us/articles/360025595512-Copying-column-group-headers-when-using-copy-with-headers

Too complex compared to its associated benefit

This is the default windows behavior for scrollers

As 'templateUrl' is a legacy property used by angular 1.x users we don't want to santize it at this late stage due to the potential impact to existing users. Note that if this property is not used by application developers it won't pose a security risk in your application.

This is the workaround, it autosizes cols first before sizing cols to fit: function sizeColsToFit() { // STEP 1: need to autosize cols first to achieve consistent results var allColumnIds = []; gridOptions.columnApi.getAllColumns().forEach(function(column) { allColumnIds.push(column.colId); }); gridOptions.columnApi.autoSizeColumns(allColumnIds); // STEP 2: then size cols to fit gridOptions.api.sizeColumnsToFit(); } https://plnkr.co/edit/02RGrvx6f0VESIQJqPKz?p=preview Note the reason for this inconsistent behaviour is due to the algorithm uses a ratio of widths and takes the actualWidths into account, but these are successively changing. The workaround ensure that each time we call sizeColumnsToFit() the actualWidths will be the same each time.

As stated in the docs, this is very difficult to combine, so there are no plans to do this anytime soon

Workaround in our KB https://ag-grid.zendesk.com/hc/en-us/articles/360020323071-Adding-cut-support

It turns out this is much more difficult than anticipated, we won't be able to deliver this

We are adding a side button to the grid, we are hoping to shortly add the ability to add more side panels/hide already shown, we think this should will cover the same functionality but it will be more flexible.
Check the documentation for tool panel. Tool panel has been revamped and changed considerably from v16