Skip to content
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

primeng 16 forces a default height of 200px on the listbox #15450

Closed
nesanmano opened this issue May 3, 2024 · 1 comment
Closed

primeng 16 forces a default height of 200px on the listbox #15450

nesanmano opened this issue May 3, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@nesanmano
Copy link

nesanmano commented May 3, 2024

I have an serious problem. My app has a sidebar (div)with overflow enabled. We construct a menu using the listbox component. The problem is the when we expand a listbox it has a scroll bar because the number of items are greater than the visible area. If I we remove the 200px height, all the items(listboxes) can be fully expanded. The problem is the div containing the listboxes is scrollable beyond the maximum number of listboxes that it contains. In other words, we have a huge white spaces after the last listbox component We did not have this problem in the previous versions of primeng. I went to check the code on the repo and they are not the same. As of version 16.9 we have the scrollHeight.?

@github-actions github-actions bot added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 3, 2024
@nesanmano nesanmano changed the title primeng 16.6 forces a default height of 200px on the listbox primeng 16 forces a default height of 200px on the listbox May 3, 2024
@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?

Thanks a lot for your understanding!
Best Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants