Removing columns interferes with frozen columns
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
From @ryanjmackinnon on April 3, 2017 13:25
When I have a grid with frozen columns and remove columns meaning there are now less columns than the frozen column count, I get odd behaviour including a spurious column being left in, and the styling showing the frozen class still applied to the columns.
For example Grid has columns A-G. C is the last frozen column. I remove columns A-E and G leaving only F visible. As part of this process I set frozenColumnCount to 0.
Expected: to see only column F and it not be frozen.
Actual: I see F and G, and F has frozen styling.
It appears that the setFrozenColumnCount is not being applied when column changes are also applied.
If I remove A-D first, and then E&G separately, F is then displayed correctly.
If I use setHidden(true) instead of removing the columns, it also works, but we are not wanting to do this for out application
Example grid page showing a variation of the issue here:
MyUI.txt
Copied from original issue: vaadin/vaadin-grid#844
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
Start with the attached MyUI.txt example and reproduce the case where columns A-E and G are removed while frozenColumnCount is set to 0. Trace the grid's column-removal and frozen-column update handling; done means only column F remains visible and it no longer has frozen styling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100