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

Dropdown Component #14190

Closed
marinija opened this issue Nov 23, 2023 · 6 comments
Closed

Dropdown Component #14190

marinija opened this issue Nov 23, 2023 · 6 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@marinija
Copy link

Describe the bug

property [autoDisplayFirst]="true" not working anymore, it's not auto selecting the first dropdown option

Environment

Angular version 16, 16.9.0

Reproducer

No response

Angular version

16.0.0

PrimeNG version

16.9.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.14.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@marinija marinija added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 23, 2023
kkoripl pushed a commit to kkoripl/primeng that referenced this issue Dec 20, 2023
kkoripl pushed a commit to kkoripl/primeng that referenced this issue Dec 20, 2023
@alexnoise79
Copy link
Contributor

alexnoise79 commented Dec 29, 2023

1 Major and 3 minor releases and still this is not fixed? how possible?

@alexnoise79
Copy link
Contributor

@yarikwest
Copy link

yarikwest commented Dec 29, 2023

1 Major and 3 minor releases and still this is not fixed? how possible?

See #14426

@PeterHewat
Copy link

1 Major and 3 minor releases and still this is not fixed? how possible?

See #14426

It's a pity the documentation hasn't been updated: https://primeng.org/dropdown#api.dropdown.props.autoDisplayFirst

@digitalcraftco
Copy link
Contributor

digitalcraftco commented Jul 10, 2024

How do we handle async use cases now? Without a placeholder the dropdown is blank. Even harder if the options are frozen from state.

<div *ngIf="sendToChoices$ | async as options; else showLogin">
 <p-dropdown [(ngModel)]="comMethod" [options]="options" ></p-dropdown>
</div>

@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 reopen the issue so we can include it in our roadmap?
Please don't forget to add your feedback as a comment after reopening the issue. These will be taken into account by us and will contribute to the development of this feature. 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

Successfully merging a pull request may close this issue.

6 participants