Hi Paul,

This is one of those features that sound nice and clear as a concept, but are very infeasible to implement and don't work in a reliable way.

• The Grid can't know how high the rows will be unless it renders them. This will slow down the data binding. We may impose a limitation for the developer to set a fixed RowHeight. This will still not resolve scenarios like hierarchy or grouping.
• The Grid height can change as a result of different user actions or application features. For example, the Grid may be inside another resizable container that doesn't depend on the browser viewport size. We can easily detect browser window resize, but pretty much nothing else, unless you do that yourself and use some method to refresh the Grid manually.
• Even when the feature works, it may cause flickering.
• The suggested feature requires a breaking change in the PageSize parameter type. So it will affect everybody that doesn't use the feature.

That's why my suggestion is to implement a custom algorithm that suits your specific use case. It will be a lot simpler and more reliable that a universal built-in algorithm.

Regards,
Dimo
Progress Telerik