-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frozen columns - overlap on hover #3554
Comments
This is not reproducable with the example from the documentation at least: https://vaadin.com/docs/v14/ds/components/grid/#columns. Can you please provide a minimal reproducable code example to test this? Also note that the latest version for Vaadin 14 is A related issue for editable cells in |
2022-08-09.at.16-19-58.mp4You can see the uploaded video, so currently i`m using 14.8.6, but i have mentioned 14.8.14 because i switched to it just to check whether i`ll have the same behavior, and i have it. So i`m using |
@poison4o Please provide a code example that reproduces the issue, from the video it's not clear what you are doing that could cause the issue. As I mentioned above, for a simple case like the one demonstrated in the docs, the issue does not occur, so there must be something specific to how you setup the grid. |
So the problem is on my side, i found out, that there is a custom css which is causing the problem, so the issue is fixed |
Description of the bug
If you have a frozen column(s), and you have some other column(s) under the frozen, on hover the row, the value of the back column(s) overlap the value of the frozen column(s). This is also tested with the latest version of vaadin 14.8.14
Expected behavior
The value of the column(s) that is under the frozen column(s) shouldn`t be visible
Minimal reproducible example
When you have a frozen column, and you want to scroll(horizontal scroll), the other columns will go under the frozen column(s), which is fine but when you just hover the row, you will see that the value that is under frozen column(s) is showing.
You can check the https://postimg.cc/GHYK5SrK
Versions
The text was updated successfully, but these errors were encountered: