-
Notifications
You must be signed in to change notification settings - Fork 108
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
Improved usage of VDataTableVirtual #2291
base: master
Are you sure you want to change the base?
Conversation
- Pass ref to ensure correct row height measurement - Introduced GScrollContainer Component to indicate more content is available - Optimized worker, ticket labels and access restrictions layout on cluster list - Use VDataVirtual for Secret & Member Page - Introduced useTwoTableLayout composable for optimized two table page layouting
@grolu You need rebase this pull request with latest master branch. Please check. |
const { height: containerHeight } = useElementSize(containerRef) | ||
|
||
const desiredFirstTableHeight = computed(() => { | ||
const contentHeight = firstTableItemCount.value * (itemHeight + 1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why +1?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well I added this to try to compensate the fact that the table adds srollbars even if the calculated height matches exactly the content height. Looking at it now it seems to only make it worse. Let's remove it.
there is also a conflict that has to be solved. In addition, I noticed the following bug (as discussed offline) Go to some Project, make sure to deselect the worker column from the table options |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: