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 #14751

Closed
NrujalSharma opened this issue Feb 7, 2024 · 6 comments
Closed

Component: Dropdown #14751

NrujalSharma opened this issue Feb 7, 2024 · 6 comments

Comments

@NrujalSharma
Copy link
Contributor

Describe the bug

Selected values in dropdowns are not rendering within the input box of a dropdown but on expanding options the option shows selected.

Dropdown options come from a signal and dropdown value comes from a separate API call
The behaviour is unpredictable as the value renders sometimes and sometimes it doesn't. Looks like some race condition issue.

PFA

image
image

Environment

Windows 11

Reproducer

No response

Angular version

~17.0.10

PrimeNG version

^17.3.2

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.11.0

Browser(s)

Chrome, Edge

Steps to reproduce the behavior

No response

Expected behavior

If a dropdown field has a value assciated with it, the selected value should be rendered within the input box

@NrujalSharma NrujalSharma added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 7, 2024
@laurz94
Copy link

laurz94 commented Feb 7, 2024

I am having a similar problem. The dropdown knows which option is selected, but the value is not displayed when selected.

"@angular/core": "^16.2.10",
"primeng": "^16.9.1",
"typescript": "~4.9.5"

@laurz94
Copy link

laurz94 commented Feb 7, 2024

Works in 16.6. Breaks in 16.7

@Dharmang92
Copy link

This issue also comes for dropdowns which doesn't have a default value assigned.

@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Feb 8, 2024
@cetincakiroglu
Copy link
Contributor

Hi,
Could you please share a stackblitz example so we can identify the issue?

@cetincakiroglu cetincakiroglu added the Resolution: Needs More Information More information about the issue is needed to find a correct solution label Feb 12, 2024
@cetincakiroglu cetincakiroglu added this to the 17.7.0 milestone Feb 12, 2024
@NrujalSharma
Copy link
Contributor Author

@cetincakiroglu
Upgrading to 17.6.0 fixed the issue for us

@cetincakiroglu
Copy link
Contributor

Hi @NrujalSharma,

Thanks a lot for the feedback, I'm closing the issue since it doesn't exist anymore.

@cetincakiroglu cetincakiroglu removed Type: Bug Issue contains a bug related to a specific component. Something about the component is not working Resolution: Needs More Information More information about the issue is needed to find a correct solution labels Feb 13, 2024
@cetincakiroglu cetincakiroglu removed this from the 17.7.0 milestone Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants