Row Spanning

By default, each cell will take up the height of one row. You can change this behaviour to allow cells to span multiple rows. This feature is similar to 'cell merging' in Excel or 'row spanning' in HTML tables.

Configuring Row Spanning

To allow row spanning, the grid must have property suppressRowTransform=true. Then row spanning is set configured at the column definition level. To have a cell span more than one row, return how many rows to span in the callback colDef.rowSpan.

// turn off row translation gridOptions.suppressRowTransform = true; // row span is 2 for rows with russia, but 1 for everything else colDef = { headerName: "Country", field: "country", rowSpan: function(params) { return params.data.country==='Russia' ? 2 : 1; } ... }; The property suppressRowTransform=true is used to stop the grid positioning rows using CSS Transform and instead the grid will use CSS Top. For an explanation of the difference between these two methods see the blog JavaScript GPU Animation with Transform and Translate . The reason row span will not work with CSS transform is that CSS transform creates a stacking context which constrains CSS z-index from placing cells on top of other cells in another row. Having cells extend into other rows is necessary for row span which means it will not work when using CSS translate. The down side to not using transform is performance, row animation (after sort or filter) will be slower.

The interface for the rowSpan callback is as follows:

// function you implement on the column definition function rowSpan(params: rowSpanParams) => number; interface RowSpanParams { node: any, // row node in question data: RowNode, // data for the row colDef: ColDef, // the col def for the column column: Column, // the column object in question api: GridApi, // the grid's API columnApi: ColumnApi, // the grids column API context: any // the provided context }

Row Spanning Simple Example

Below shows a simple example using row spanning. The example doesn't make much sense, it just arbitrarily sets row span on some cells for demonstrations purposes.

  • The athlete column is configured to span 2 rows for 'Aleksey Nemov' and 4 rows for 'Ryan Lochte'.
  • The athlete column is configured to apply a CSS class to give background to the cell. This is important as if background was not given, the cell background would be transparent and the underlying cell would still be visible.

Row Spanning Complex Example

Row spanning will typically be used for creating reports with ag-Grid. Below is something that would be more typical of the row spanning feature. The following can be noted from the example:

  • Column Show row spans by 4 rows when it has content.
  • Column Show uses CSS class rules to specify background and border.
  • Column Show has a custom cell renderer to make use of the extra space.

Constraints with Row Spanning

Row Spanning breaks out of the row / cell calculations that a lot of features in the grid is based on. If using Row Spanning, be aware of the following:

  • Responsibility is with the developer to not span past the last row. This is especially true if sorting and filtering (eg a cell may span outside the grid after the data is sorted and the cell's row ends up at the bottom of the grid).
  • Responsibility is with application to apply background style to spanning cells so that cells overwritten cannot be seen.
  • Overwritten cells will still exist, but will not be visible. This means cell navigation will go to the other cells - eg if a row spanned cell has focus, and the user hits 'arrow down' key, the focus will go to a hidden cell.
  • Row span does not work with dynamic row height or auto-height. The row span assumes default row height is used when calculating how high the cell should be.
  • Sorting and filtering will provide strange results when row spanning. For example a cell may span 4 rows, however applying a filter or a sort will probably change the requirements of what rows should be spanned.
  • Range Selection will not work correctly when spanning cells. This is because it is not possible to cover all scenarios, a range is no longer a perfect rectangle.