Grid scroll bar and scrolling gets broken in Chrome and Firefox
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
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:
- You need a container with enough rows that cannot be shown in the window at the time.
- You need filter in the container to restrict shown rows.
- First show data in the grid with filter on, so that you have less rows and no scroll bar appears (this is correct)
- 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)
- Click scroll bar to jump to end of the list with the mouse, the view will update correctly
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Grid state described in the issue: filter to remove the scrollbar, disable the filter, jump to the end, then return to the beginning in Chrome and Firefox. Start by tracing the Grid scrolling and row-rendering behavior involved in that sequence. Done means the view and rendered rows continue updating correctly when the scrollbar is moved in both browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100