Skip to content

Conversation

@dimodi
Copy link
Contributor

@dimodi dimodi commented Mar 7, 2025

No description provided.

@dimodi dimodi added the merge-to-production Use this label to get a comment to choose whether to merge the PR to production label Mar 7, 2025
@dimodi dimodi requested review from a team as code owners March 7, 2025 13:10
@github-actions
Copy link
Contributor

github-actions bot commented Mar 7, 2025

Hello @dimodi,

Check the below option if you would like to automatically generate PR to production. The automation uses the branch for the cherry-pick, and then will delete the branch. Please, do not delete it manually.

  • create PR to production

@dimodi dimodi merged commit bfcaf60 into master Mar 11, 2025
@github-actions
Copy link
Contributor

Here you are the link to your PR to production: 2818

@github-actions github-actions bot deleted the grid-virtual-revamp branch March 11, 2025 13:04
});
}
}
Set the `PageSize` value, so that the rendered table rows do fit in the [Grid height](#height). At least one table row must be completely invisible.Otherwise, empty row skeletons may display in the Grid while users are not scrolling. The exact `PageSize` value allows you to balance between better user experience and data request efficiency:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Set the `PageSize` value, so that the rendered table rows do fit in the [Grid height](#height). At least one table row must be completely invisible.Otherwise, empty row skeletons may display in the Grid while users are not scrolling. The exact `PageSize` value allows you to balance between better user experience and data request efficiency:
Set the `PageSize` value so that the rendered table rows fit in the [Grid height](#height). At least one table row must be completely invisible. Otherwise, empty row skeletons may display in the Grid while users are not scrolling. The exact `PageSize` value allows you to balance between better user experience and data request efficiency:


The `RowHeight` value must be large enough to accommodate the cell content in all rows, even if the content differs. In other words, the `RowHeight` setting must apply the same or greater table row height than what the browser would normally render. The effective row height depends on:

* The cell content and text wrapping
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* The cell content and text wrapping
* The cell content and text wrapping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-to-production Use this label to get a comment to choose whether to merge the PR to production

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants