We have a PrimeNG table with Paginator and lazy loading. We’ve run into an issue where the user can set a very large number for the offset parameter through the url. If the offset parameter is larger than the index of the last record in the table, the default behaviour is for the paginator to keep scrolling the pages backwards until it finds a record. The problem is that it keeps hitting the backend unnecessarily, leading to potential performance issues.

Is there any way to disable this default behaviour of reverse scrolling please? We’re using Prime 17.

We tried adding some custom logic to prevent this behaviour and it worked, but we want to avoid having to add custom logic to each table if possible.

Thanks