VScrollTable pagelength is set to 0 when table has size lower than displaying 1 row completely breaking lazy loading

[Enerccio]

https://github.com/vaadin/framework/blob/aa3757c6649fa056b9495500d6987d213a8bb782/compatibility-client/src/main/java/com/vaadin/v7/client/ui/VScrollTable.java#L6866

This is a huge bug because if you have resizable table (such as in split panel) if you resize table to 0 (hiding it), it will completely disable lazy loading, loading all items from database!

[Ansku]

I don't have time to test this right now, but does it help with the issue if you override the server-side getPageLength() to always return 1 at minimum?

[Enerccio]

I fixed it in git build we use by changing client code to report rowsAtOnce at least 1, not sure if it breaks anything else but it fixes the bug

[stale[bot]]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!