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

Component: Dropdown -virtualScroll UI issue #16991

Closed
vishalsoni007 opened this issue Dec 10, 2024 · 2 comments
Closed

Component: Dropdown -virtualScroll UI issue #16991

vishalsoni007 opened this issue Dec 10, 2024 · 2 comments
Labels
Status: Pending Review Issue or pull request is being reviewed by Core Team

Comments

@vishalsoni007
Copy link

Describe the bug

In version17(^17.18.12), Basic dropdown work properly but if add [virtualScroll]="true" [virtualScrollItemSize]="38" then options not showing in expand panel. this issue is on primeNg offical website too.

Environment

 "@angular/common": "^18.0.0",
"primeng": "^17.18.12",

Reproducer

No response

Angular version

18.0.0

PrimeNG version

17.18.12

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

22

Browser(s)

Chrome 110

Steps to reproduce the behavior

  1. Add p-dropdown with virtualScroll
  2. On click of that expand panel is not visible properly.

Expected behavior

After click on dropdown with virtualScroll it should get expand properly for select options

@vishalsoni007 vishalsoni007 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Dec 10, 2024
@mertsincan mertsincan added this to the 17.18.14 milestone Dec 11, 2024
@github-project-automation github-project-automation bot moved this to Review in PrimeNG Dec 11, 2024
@mertsincan mertsincan added Status: Pending Review Issue or pull request is being reviewed by Core Team and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Dec 11, 2024
@meursj
Copy link

meursj commented Dec 13, 2024

The bug was introduced in version 17.18.13, in 17.18.12 it worked ok

See also #17039

@mertsincan
Copy link
Member

Fixed in #17039

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Review Issue or pull request is being reviewed by Core Team
Projects
None yet
3 participants