-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Scroller/Tree/TreeTable/Table: VirtualScrolling does not work after upgrading to PrimeNG 18 from 17.18.12 #17102
Comments
STill broken in 18.0.2 and 19.0.1. (Angular 18 and 19). Here is v19 branch for reference https://github.com/BeGj/primeng-18-virtualscrolling-flex-height-bug/tree/angular19 |
It works in 17.18.15 (V17 branch for reference https://github.com/BeGj/primeng-18-virtualscrolling-flex-height-bug/tree/v17) Something went wrong here: 17.18.15...18.0.0 |
I ran into that problem, too, and added a style to solve it:
|
This did not work in my sample provided above, and neither in my production code.. I added this to styles.scss :host ::ng-deep .p-datatable-flex-scrollable p-scroller {
height: 100%;
width: 100%;
} Did I do it wrong, or do you have any further instructions? |
thank you! worked for me |
Thank you, that did the trick for |
Describe the bug
Whenever you are using a
virtualScroll
together withscrollHeight: flex
it will not work. Nothing will display.I have tested on three different components
Se attached repository for the TreeComponent. Since all these component use p-scroller under the hood I think it's likely something wrong with p-scrolller
Environment
See package.json
Reproducer
https://github.com/BeGj/primeng-18-virtualscrolling-flex-height-bug
Angular version
PrimeNG version
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
v20.18.0
Browser(s)
firefox 133 and chrome 129 and chromium 133
Steps to reproduce the behavior
Expected behavior
Expects the virtual scrolling to work! Or at least dislay something like previously...
The text was updated successfully, but these errors were encountered: