Grid scroll bar and scrolling gets broken in Chrome and Firefox

[vaadin-bot]

Originally by @TatuLund

---

In my bugrap implementation I observed the following issue. With certain steps it is possible to get Grid to faulty state.

Steps to reproduce:

1. You need a container with enough rows that cannot be shown in the window at the time.
2. You need filter in the container to restrict shown rows.
3. First show data in the grid with filter on, so that you have less rows and no scroll bar appears (this is correct)
4. Then disable filter (e.g. using button toggle in the UI), so that more rows are shown. Now scroll bar appears on the right (this is correct)
5. Click scroll bar to jump to end of the list with the mouse, the view will update correctly
6. Click scroll bar to jump to begining of the list. Now the content is not being updated correctly and moving scroll bar doesn't have effect anymore. It maybe also that some rows are not rendered correctly or left empty.

The following seems to work ok with Internet Explorer, the error happens with Chrome and Firefox.

If you need more information, I can demostrate this with my computer.

---

Imported from https://dev.vaadin.com/ issue #18017

[vaadin-bot]

Originally by @TatuLund

---

Attachment added: Grid-issue.JPG (167.3 KiB) https://trac-attachments.vaadin.com/trac/18017/Grid-issue.JPG Screenshot

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

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!

[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!