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

Multiselect: VirtualScroll viewport doesn't resize correctly when searching #13692

Closed
LinusSee opened this issue Sep 18, 2023 · 3 comments
Closed
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@LinusSee
Copy link

Describe the bug

When scrolling in a multiselect with virtual scrolling and then searching for an item, the viewport size becomes too small to display any items.

Environment

Reproducable using PrimeNg Docs https://primeng.org/multiselect#virtualscroll.
I checked the docs for v15 and v16 and was able to reproduce the bug in both.

Reproducer

No response

Angular version

16

PrimeNG version

16.3.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16

Browser(s)

Firefox 117, Chrome 116, Edge 117

Steps to reproduce the behavior

To recreate you can use the virtual scroll example from the docs https://primeng.org/multiselect#virtualscroll.

  1. Scroll down a few items e.g. "Item 50"
    1_MultiselectVirtualScrollBug

  2. Search for a specific item (to reduce the number of items displayed to 1)
    2_MultiselectVirtualScrollBug

  3. Viewport size is too small to display any items
    3_MultiselectVirtualScrollBug

Expected behavior

The viewport should have a size necessary to display found items.

@LinusSee LinusSee added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Sep 18, 2023
@admt1
Copy link

admt1 commented Oct 23, 2023

Same issue here, i need to use virtualScroll, but it's not resizing

@Romain-Luengo
Copy link

Same here

@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

4 participants