Next Release Target: 11th Dec (v25.0.0)

This isn't a bug or a regression in ag-Grid. The internals of the DOM are always subject to change without notification (with the exception of CSS/styling related changes). Adding the line below: browser.ignoreSynchronization = true; to the top of the test will fix this. This will work around this issue in Protractor.

Grid is working as expected. The defaultColDef is not getting taking into consideration when calling setColumnState. For example this: gridOptions.api.setColumnDefs([ { field: 'athlete' }, // stays { field: 'country' }, // Flex value changes on this column { field: 'sport', flex: undefined }, // Flex value stays on this column { field: 'gold' }, ]); When: defaultColDef: { flex: 1, }, Actually means this: gridOptions.api.setColumnDefs([ { field: 'athlete', flex: 1 }, // stays { field: 'country', flex: 1 }, // Flex value changes on this column { field: 'sport', flex: undefined }, // Flex value stays on this column { field: 'gold', flex: 1 }, ]); Also note that "flex: undefined" means don't touch flex. If you want to clear it though a column update, should use "flex: null".

Yes this is a regression, however it was done on purpose. Before 'sizeColumnsToFit()' resized columns based on their current widths. This was indeterministic, as each time you called it, the columns could end up different widths. This was causing issues when columns were shown / hidden then resized (eg user is expanding / collapsing column groups repeatedly and calling sizeColumnstoFit() after each expand/collapse) - in this scenario some columns ended up shrinking. Now 'sizeColumnstoFit()' resizes columns based on the width defined on the Column Definition. This means each time it's called, the columns end up the same width. If the user wants columns to have different widths, then set different initial widths in the Column Definitions of use Flex Columns feature.

It's invalid to focus an element that isn't focusable (a div) - Chrome blocks this behavior by default, but Firefox sends focus back to the body of the page. This is browser behavior that we cannot workaround. This is not an issue with ag-Grid. The fix for this is to add a tabIndex property to the element you need to be focusable as shown below: https://plnkr.co/edit/YNZlgvlvxeU6iDN2

This behavior is caused by an issue in Chrome with editor caret placement when using RTL languages. You can reproduce this same caret placement issue without ag-Grid at all, with a simple text input as shown in sample below (note we're setting dir="rtl" on the HTML element of this page): https://plnkr.co/edit/L5NHE82OQj6jpiSl Please open sample in Chrome/Edge - you can see the caret location set incorrectly. Please open sample in Firefox/Internet Explorer 11 - caret location is set correctly. This is why this caret placement issue is due to a bug in Chrome. As this behavior isn't specific or related to ag-Grid we've now closed this issue.

Issue cannot be reproduced after clearing the browser cache.

The Server-Side Row Model (SSRM) has received a huge update with regards how it works to allow all of the following features: + Ability to turn off infinite scrolling, so all rows are read back for a particular group. This was implemented by introducing the concepts of Row Stores. The Partial Store provides Infinite Scrolling (backwards compatible approach) and the Full Store reads all records in one go without using Infinite Scrolling. The concept of Full Store (reading all rows at once) paved the way for SSRM Transactions and Client Side Sorting & Filtering. See https://www.ag-grid.com/javascript/server-side-model-row-stores/ + Sorting and Filtering now occur on the client side rather than the server side if all rows are read back from the server (via the Full Store). See https://www.ag-grid.com/javascript/server-side-model-sorting/ and https://www.ag-grid.com/javascript/server-side-model-filtering/ + Support for Transactions to allow Updates, Inserts and Removes of data on the client side. See https://www.ag-grid.com/javascript/server-side-model-transactions/ + Support for Async Transactions to allow a high frequency of Updates, Inserts and Removes. This is brilliant for showing updates to large data that is changing at a rapid pace (eg many updates per second). See https://www.ag-grid.com/javascript/server-side-model-high-frequency/ + Refreshing of rows (as apposed to purging) to allow reloading rows in the background without showing loading spinners to the user. See https://www.ag-grid.com/javascript/server-side-model-refresh/ + Refreshing of rows doesn't loose group state if groups are expanded. See https://www.ag-grid.com/javascript/server-side-model-refresh/#group-state + Failed fetching of data can now be retried at a later point. See https://www.ag-grid.com/javascript/server-side-model-retry/ + Groups can now be opened by default using the grid callback isServerSideGroupOpenByDefault(). See https://www.ag-grid.com/javascript/server-side-model-grouping/#open-by-default + New API for expanding all groups, see https://www.ag-grid.com/javascript/server-side-model-grouping/#expand-all--collapse-all + Customisation of Store (Cache) properties at different levels. Eg have block size of 100 on top level, and 500 on lower levels. Or use Full Store at top levels and Partial Store at other levels. See https://www.ag-grid.com/javascript/server-side-model-grouping/#configure-stores + 'Store Info' can be provided when loads complete, which can then be viewed using Store State. See https://www.ag-grid.com/javascript/server-side-model-grouping/#store-state--store-info
These two breaking changes only apply if using the Server-Side Row Model. 1) There is a new property serverSideStoreType which must be set to 'partial'. Stores are a new concept and there are two store types, 'partial' and 'full'. It was decided to make 'full' the default despite this decision creating a breaking change. The reason is that 'full' is what most people will probably use and is easier to learn before moving to 'partial', thus it's a breaking change for all current users with the value of simplifying how the SSRM works. 2) The undocumented property RowNode.childrenCache is now called RowNode.childStore. As this is an undocumented property, nobody should be using it. However if you are using it, it's now changed. 3) purgeServerSideCache is deprecated, replaced with refreshServerSideStore which provides the same functionality but with purge=true as an option. This allows for silent refreshes without showing the loading indicator, but instead updating the data in place.

New property added showOpenedGroup. When showOpenedGroup=true, then group columns will show the opened group.

After profiling the grid with the provided example, it showed getColumn() method in Column Controller was a bottleneck. This was doing looping over columns. Now instead the columns are also stored in a map (ID -> Column) and the map is now used instead of looping over the list. This gives a performance boost.