AG Grid 36.1.0: cellRenderer IS called on initial paint with async rowData (36.1.0 CDN)
Comments · 0
Be the first to comment.
Explanation— by SceneRecap AI
The recording demonstrates cell renderer behavior in AG Grid version 36.1.0 when handling asynchronous row data. From the start at [1.0s], an AG Grid table titled "AG Grid 36.1.0 — cellRenderer with async rowData" displays eight populated rows across two columns: "plain (field only)" and "custom (cellRenderer)". The top status line indicates that initial rendering triggered eight renderer calls (rendererCalls=8 | custom cells=8 blank=0), confirming that each cell renderer successfully executed and populated values without leaving blank cells.
At [12.6s], the user clicks the refreshCells({force:true}) button located beneath the grid. Following this action, by [15.0s], the status line updates to show that the call count has increased to rendererCalls=16 | custom cells=8 blank=0, verifying that forcing a cell refresh re-executes the cell renderers for all eight rows while maintaining proper custom cell rendering without blanks through the end of the recording at [22.0s].
Key moments
What to know
- •On initial load, AG Grid 36.1.0 executes the custom cellRenderer once for each of the 8 asynchronously loaded rows without leaving blank cells.
- •Clicking the refreshCells({force:true}) button re-invokes the cell renderer across all rows, doubling the total rendererCalls count from 8 to 16.
Glossary
- cellRenderer
- An AG Grid component or function used to customize the display and rendering logic of individual table cells.
- refreshCells
- An AG Grid API method that forces cells to re-render, optionally ignoring change detection when {force: true} is specified.
Your recordings could explain themselves too.
Free plan · silent recordings welcome · bug reports included.
Try SceneRecap free →