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

grouped p-dropdown value setting is not working using [(ngModel)] #5246

Closed
ASK83 opened this issue Mar 2, 2018 · 1 comment
Closed

grouped p-dropdown value setting is not working using [(ngModel)] #5246

ASK83 opened this issue Mar 2, 2018 · 1 comment
Assignees

Comments

@ASK83
Copy link

ASK83 commented Mar 2, 2018

There is no guarantee in receiving an immediate response in GitHub Issue Tracker, If you'd like to secure our response, you may consider PrimeNG PRO Support where support is provided within 4 business hours

I'm submitting a ... (check one with "x")

[X] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Current behavior
When using grouped p-dropdown the value cannot be set using ngModel.

Expected behavior
Whenever there is a predefined value linking the p-dropdown to a value the value should be set like the regular p-dropdown

Minimal reproduction of the problem with instructions
Here is the link I am showing the issue with grouped p-dropdown vs simple p-dropdown
http://plnkr.co/edit/RNHTvMjGuPXEgmpqC7hE?p=preview

What is the motivation / use case for changing the behavior?
It is a common use case to have default values for the dropdown that needs to be set.

Please tell us about your environment:

  • Angular version: 2.0.X
    @angular 5.2.5

  • PrimeNG version: 2.0.X
    5.2.0

  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
    All of them

  • Language: [all | TypeScript X.X | ES6/7 | ES5]
    Typescript

  • Node (for AoT issues): node --version =
    8+

@cagataycivici cagataycivici self-assigned this Apr 18, 2018
@cagataycivici cagataycivici added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Apr 18, 2018
@cagataycivici cagataycivici added this to the 5.2.5 milestone Apr 18, 2018
@cagataycivici cagataycivici added Status: Pending Review Issue or pull request is being reviewed by Core Team and removed Status: Pending Review Issue or pull request is being reviewed by Core Team labels Apr 18, 2018
@cagataycivici cagataycivici removed this from the 5.2.5 milestone Apr 19, 2018
@cagataycivici
Copy link
Member

Fixed via;

#5080

@mertsincan mertsincan removed the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Oct 18, 2018
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

3 participants