-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Scroll loading does not work if the table is not displayed completely horizontally #862
Comments
Hi @vegegoku, |
The issue is a little bit complicated it seems because the scroll bars. zoom and other factors affect the calculation for the scroll reaching the bottom, and it seems it has different behavior for different browsers. we have added an offset as part of the plugin config to make it configurable so the scrollbar does not need to reach the exact bottom , try playing with that while I investigate the issue again. |
It is working on chrome, can you please prepare a reproducible project for this. I am not sure now what is causing the issue for you/ |
Seems to depend on the display resolution. I previously tested on 3840x2160. When changing to 1920x1080 it works for me as well in Chrome. |
This is on a much higher resolution |
My project to reproduce |
This does not seems to be right, that seems to be taken from an old commit, why not try the latest HEAD-SNAPSHOT instead |
I have the same problems when compiling the development branch of the domino-ui-demo using SNAPSHOT-HEAD as it is in this commit DominoKit/domino-ui-demo@85a6c24. |
Describe the bug
When having a table, that is not displayed completely horizontally, the scroll loading does not work as expected. When scrolling down to the last entry, new entries are displayed only sporadically. Problem appears on v1 and v2.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The scoll loading should load new entrties even if the table is not completely displayed horizontally, which may be the default case when having many columns.
Desktop:
The text was updated successfully, but these errors were encountered: