Next Release Target: 23rd Apr (v25.2.0)

To work around this issue, you should apply the CSS property display: inline-block; to the parent div (has a class of 'ag-react-container'). This will negate the default "block" display type of the div, so it should show inline with the other elements. This can be seen here: https://next.plnkr.co/edit/lEgeFZy4gE13dFeI

You can workaround this issue by setting the gridOptions rowBuffer property to a larger value to pre-render more rows to allow the row span to render correctly. By default rowBuffer is 20, so if you have row spans with more than 20 rows, that will cause the issue. You can fix this by setting the rowBuffer property to a value equal or bigger than the number of rows in the largest row span you have. For example, so if your biggest row span is 100 rows, set rowBuffer to 100 to resolve this as shown here: https://plnkr.co/edit/syUbfeLUnYFEXhxJ Note that in this example the row span is correctly shown as you scroll down. The rowBuffer property is documented here: https://www.ag-grid.com/documentation/javascript/grid-properties/ Please keep in mind that using a larger value for rowBuffer will increase the memory footprint, as it pre-renders a larger number of rows before they're scrolled into view.

You can implement this using a CSS workaround as shown here: https://plnkr.co/edit/UVo1rPgCqSaZT16k

You can implement named ranges for filtering "Last week", "This Week", etc. using custom filter operators as shown here: https://plnkr.co/edit/sxpucQP1Hn3srQcS

This is implemented in the sample below. The ATHLETE column is marked as "rowheader" column. Note the screen reader announcement for the cells in the AGE column start with announcing the value of the ATHLETE column in that same row. Steps to follow: 1. Open JAWS 2. Open https://plnkr.co/edit/QszQ1uyDFVdtHq0v?preview 3. Focus the top cell in the AGE column *Actual & Expected*: Announcement is "Michael Phelps 23"

Workaround - provide event source via the grid context. In sample below, note the setting of the grid context and reading this context in the onColumnVisible event to determine the source of the event (whether it's manual or in response to a call to applyColumnState). Please follow the steps below for an illustration: 1. Open https://plnkr.co/edit/q7Hpn9MyO2qe1Nlr 2. Open dev console 3. Click Toggle Price column button (edited) Actual & Expected; Message in dev console indicating that column visible was called in response to restoring state = false 4. Click Reset columns button Actual & Expected; Message in dev console indicating that column visible was called in response to restoring state = true

You can implement this behavior using the approach and samples here: https://blog.ag-grid.com/deleting-selected-rows-and-cell-ranges-via-key-press/

This filter behavior can be added to the default filter with a custom filter option as illustrated here: https://plnkr.co/edit/jaAXviTMWrEAoedd

Workaround: https://plnkr.co/edit/xngeA6Ixzzr2d9Yq The code is getting the value formatter separately for group rows.

Use the columnKeys property to provide the list of columns you want to export. See this implemented in the sample below - click the button above the grid to export to Excel without the ATHLETE column: https://plnkr.co/edit/380kkuz9TCT1UxE0

You can implement this in user code as shown here: https://ag-grid.zendesk.com/hc/en-us/articles/360018518798

In order to auto-size columns which are currently not in view, please turn off column virtualization by setting suppressColumnVirtualisation=true This is covered here: https://www.ag-grid.com/react-grid/column-sizing/#auto-size-columns

Workaround - while in Japanese Hiragana input mode, select a cell, press ENTER key to start editing, then you can enter Japanese text

You can implement this by showing a dummy column only in the case no other columns are visible to allow access to the column menu. This approach is implemented here: https://plnkr.co/edit/40OvlMuxC8u6sByU

Can be workaround with: function isEditable(colId, rowIndex) { return gridOptions.columnApi.getColumn(colId).isCellEditable(rowIndex); }

******* 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

Please implement this functionality in user code following the approach illustrated here: https://blog.ag-grid.com/wrapping-column-header-text/

You can implement row grouping for columns with null/undefined values as follows: https://plnkr.co/edit/rNC5GYdmRLR9Y4LZ

You can implement this when using server-side row model with infinite scrolling using the approach described below. If you have a block size of 200 and want to start loading the next block (with rows 200-400) as soon as the user is scrolling past row index 100, you need to set rowBuffer=100. This way when the user is at row 101, the grid is instantiating row 201, and as that's outside of the data for the current block 0-200, that forces a request for a new block of data (with data for rows 200-400). See this implemented here: Infinite row model - https://plnkr.co/edit/MR8mzfOAQkrGsS5s?preview Server-side row model - https://plnkr.co/edit/gEa4EdlRbVN8cjmo See the messages in the developer console indicating the second block of data is loaded much earlier as the user is scrolling, so the user doesn't see loading indicators unless they scroll really fast. If that's the case, just increase the value of cacheBlockSize to load larger chunks of data at a time to accommodate that.

This can't be fixed simply. It's to do with the hardware accelerated scrolling that iOS does. We have listeners that update the header as the body moves, however iOS is doing hardware acceleration to move the body first, then firing listeners second, so body has scrolled before grid is informed of it, thus grid lags behind.

The Grid can't be used to support this use case. Loading Overlays are intended to be used when the grid is loading data from a remote server. While the grid is processing a pivot operation, the JavaScript thread is locked up performing calculations and it's not possible to update the UI.

there are two items 1) sizeToFit flickers and 2) autoSize flickers . . . . . . the first (sizeToFit flickers) now we prefer users to use flex which doesn't have this issue and then the second (autoSize flickers), yes if you call a method on the grid from an async event, yes the grid will flicker, this applies to ALL interactions with the grid, if you call the API the grid changes! so really what we could do is 'have colDef.autoSize' so cols are autosized by default, but this is a CR not a bug

This is working as expected. When you use a column type, that is selecting default values for the Column Definition. When you provide something then in the cell that is also in the default, the provided overrides the default. So if you are going override the class, make sure the class you provide also aligns text to the left.

This work is now being tracked under AG-3709

This is expected behaviour, when rangeSelections are enabled, clicking on the same cell multiple times will create a new range for each click. If this behaviour is undesired set the gridOptions property: suppressMultiRangeSelection=true. I tried to reproduce in latest and could not. Am assuming it is fixed.

This item was previously released, but not marked as DONE. Now just marking as DONE.

This is not easy to implement. As there is no cell that was clicked on, the grid doesn't know what the column is. This is also not blocking any business functionality - user just needs to right click the cell.

In order for the cell to be refreshed, the grid needs something, either 'field' or 'valueGetter' set on the column, so it can get the value. That is the only way the grid can then tell that the value has changed and the cell needs updating. This is due to the change detection the grid does. To solve, include a valueGetter that will return a different value when the data is loaded. Demonstrated on this plunker: https://plnkr.co/edit/elOLcKx5Y6EnEwHi

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.

This functionality is currently impossible due to browser security restrictions on clipboard access. Please read additional details here: https://www.ag-grid.com/javascript-grid-clipboard/#paste-from-clipboard

We have created the following example: https://next.plnkr.co/edit/tRskkv08jyOLmmv9?preview Note that this is pretty much like a custom rewrite of the aligned grids to suit your needs.

There is a workaround in our knowledge base: https://ag-grid.zendesk.com/hc/en-us/articles/360020374692

This feature request is declined because it isn't a reasonable requirement. It's not the responsibility of the filter to test whether the condition that would produce no rows. If a user selects filter range (value > 20 && value < 10) that's a valid boolean condition, that all the filter is concerned with. Excel behaves the same way - it allows the user enter the same filtering condition (value < 10 && value > 20) and returns 0 rows without any errors/warnings.

I tried to reproduce this but couldn't. The plunker provided by the customer is no longer working. I found the description of what was going on unclear. If this is still an issue, customer can get in touch and support should provide a clearly reproducible scenario for the dev team.

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