Next Release Target: 24.0.0 (21st Aug 2020)

This is a duplicate, already fixed.

Tracked by AG-4282

This is caused by a Webkit issue - https://bugs.chromium.org/p/chromium/issues/detail?id=1073480

Working by as per design. Pinning a column by dragging will change the column order.

Keyboard navigation is not added to the expand/collapse chevron because expand/collapse action is performed and expand/collapse status is announced when focus is in the first column.

After setting new data, each Full Width Row is given the chance to refresh. This is because the grid has no way of knowing the the data has changed for this row - eg the grid doesn't know what values you are interested in. Because no refresh() method is provided on the Full Width Cell Renderer, the grid is destroying and re-creating each row, thus the row is not transitioning to the new location, as it's getting destroyed at the old location and a new row getting inserted at the new location. To get around this, include a refresh() method on the Full Width Cell Renderer. Returning 'true' tells the grid you have taken care of the refresh yourself, that you do not need the row to be re-created. Here is an updated plunker demonstrating: https://plnkr.co/edit/OeX7SYNptxUgJpbf HOWEVER - I have enhanced the functionality in ag-Grid. Now the fullWidthRows will only be asked to refresh after Transaction Update for rows where they were updated, or for rows where their parents were updated (so covers master / detail, where detail will refresh when master is updated).

This is not possible to fix. What is happening is browser is scrolling the main content using the GPU. In other words, the user is scrolling the rows left/right, by using middle mouse button scrolling, or touchpad scrolling. The GPU scrolls the rows left/right natively before firing off any events. Then the grid listens to the events and updates the position of the header. However the same GPU hardware scrolling cannot be used here, as the header is not getting natively scrolled. It is impossible for the grid to scroll the header in sync with the rows as the browsers is scrolling first the rows with GPU, then firing events second. Because of this two stage process, there is nothing the grid can do, as by the time it receives the event, it is to late. We tried to disable the GPU scrolling, however we cannot find any CSS setting to stop the GPU from getting used. It is beyond CSS & JavaScript to change this. You can also observe this between browsers that work 'well' and 'not well'. Where it does not work well, the header and rows get out of sync, however the rows are scrolling far more smoothly. Where it works well, both the header and the rows scroll at the same speed so always in sync, however the rows don't scroll as smoothly. So it's a tradeoff. In testing we found Chrome on Windows the rows and header kept in sync but rows did not scroll smoothly, however in Chrome on Mac we found the rows and header did not keep in sync, but rows did scroll smoothly. It would be nice if we introduced a property, to allow the application to choose if it wanted smooth scrolling, or synced headers / rows, however as mentioned, we could not find any CSS or JavaScript to allow this to happen. It's all in the browser implementation.

Users cannot focus the sort indicator and column menu items individually, but can trigger their actions as follows: * Press ENTER to toggle the sorting state of that column. * Press Shift + ENTER to toggle multi-sort for that column. * Press Ctrl/Cmd + ENTER to open the column menu for the focused header. * When a column menu is open, simply press ESCAPE to close it and the focus will return to the header.

user should be using groupRemoveSingleChildren instead of groupRemoveLowestSingleChildren to remove single children that are now a the lowest level.

##################################### # Column 'initial' Values ##################################### Column definitions now have 'initial' values for all stateful items. The full list of 'initial' values is as follows: initialWidth initialFlex initialHide initialSort initialSortIndex initialAggFunc initialPivot initialPivotIndex initialRowGroup initialRowGroupIndex initialPinned When a Column Definition includes an initial value, it is applied when the column is created only. It is not applied when column definitions are updated. The corresponding non-initial values are always applied, even during columns updates. For example the column definition attribute "width" is used when the column is created or any time the column definitions are updated after creation. The column definition attribute "initialWidth" is used when the column is created only. ##################################### # Gone - Immutable Columns - No longer needed ##################################### The grid property "immutableColumns" is gone. The behavior this property set is now the default (with the exception of column order, mentioned below). In the old design, when updating column definitions, if "immutableColumns=false" then column state information (width, pinned, rowGroup etc) would not be applied, as that is only applied when columns are created. By setting. If "immutableColumns=true", then column state information WAS applied. In the new design, as explained above, each state property has two variants, a "normal" and a "initial". This allows selectively applying state on creates vs updates of columns, thus "immutableColumns" is redundant. The only additional benefit to "immutableColumns" was that it applied the order of the column definitions when they were updated. To have the order applied when column definitions are updated, set the new grid property "applyColumnDefOrder=true". ##################################### # Column State Changes ##################################### Column State management has been refactored to be more flexible. A new documentation page dedicated to Column State is available here: https://www.ag-grid.com/javascript-grid-column-state/ Data returned back from gridApi.getColumnState() now additionally has the following attributes: pivot, rowGroup, sort and sortedAt. gridApi.setColumnState(state) is now deprecated and replaced with gridApi.applyColumnState(params). This allows additional parameters to be passed to the API on top of just the state. To move your code over to the new API without changing your applications functionality, instead of calling setColumnState(state), call applyColumnState({state: columnState, applyOrder: true}. When applying column state, applying the order of the columns is now optional and specified via params.applyOrder. Whey applying Column State, Columns in the grid for which no state is provided will be left untouched - previously they would be cleared of all state. Optionally a Default Column State can be applied to Columns where no state is provided. Why applying Column State, it is now possible to have attributes not applied. Eg if Column State only includes Sort information, other Column State (Row Group, Width etc) will not be impacted. The above items result in fine grained control of Column State via getColumnState() and applyColumnState() methods. ##################################### # Property suppressSetColumnStateEvents Renamed To suppressColumnStateEvents ##################################### If using property suppressSetColumnStateEvents, simply replace with property suppressColumnStateEvents. ##################################### # ColDef.sortedAt replaced with ColDef.sortIndex ##################################### If you want to sort many columns then use sortIndex rather than sortedAt to specify the order of the sorting. ##################################### # Sort State ##################################### gridApi.getSortModel() and gridApi.setSortModel() are deprecated. Sort state is now included in Column State, thus use columnApi.getColumnState() and columnApi.applyColumnState() instead.