Reputation: 68
I am using ag-grid-angular v26.1.0 in my angular (v13.3) application for most of my tables. I've noticed that for the bottom row of data only in all my table objects, the mouse pointer is not 'activated' (acknowledged) for the row to process events unless the pointer is hovered near the top third of any cell in the bottom row, as opposed to anywhere in a cell like the other rows.
Since I am configuring cellClicked event handlers and row selection handlers for various tasks to select/edit data in the table, it becomes difficult to get the placement of the mouse 'just right' on the bottom row of data to acknowledge that the mouse is indeed over the row. If I 'add' a second row of data to the table, the previously-bottom row is fine, but then the problem switches to the 'new' bottom row. Similarly, if I sort the table and the row order changes, the problem is still only associated with the sorted bottom row.
Is this by design? Or is this a bug of some sort in ag-grid-angular? If the former, is there a configuration setting I'm missing that would allow the 'entire' bottom row to be recognized when the mouse pointer is hovered over it?
Here's a sample of the configuration options I am typically specifying:
<ag-grid-angular
[ngClass]="gridTheme"
domLayout="autoHeight"
[defaultColDef]="defaultColumnDef"
[rowData]="rowData$ | async"
[columnDefs]="columnDefs"
rowSelection="single"
(selectionChanged)="onSelectionChanged()"
[frameworkComponents]="frameworkComponents"
(gridReady)="onGridReady($event)"
(cellValueChanged)="onUpdateEspConfig($event)"
(cellClicked)="onCellClicked($event)"
></ag-grid-angular>
Thanks in advance!
Upvotes: 1
Views: 708
Reputation: 68
Apparently, this is something that was introduced with the current (as of this post) version of Chrome (v105.x, still an issue in v105.0.5195.127). It worked fine in v104 and prior versions of Chrome. Not sure if this is a problem for 'other' types of scrolling grid containers or not, but it apparently is a problem for ag-grid objects that are contained in a horizontal flex container. I will post the version that fixes it if/when I come across one.
Update on Sept. 28, 2022 - Chrome v106.x appears to have fixed this problem.
Upvotes: 2