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

name property for Dropdown #4009

Closed
VeryBueno opened this issue Sep 21, 2017 · 0 comments
Closed

name property for Dropdown #4009

VeryBueno opened this issue Sep 21, 2017 · 0 comments
Assignees
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Milestone

Comments

@VeryBueno
Copy link

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

Plunkr Case (Bug Reports)
http://plnkr.co/edit/4Ct8Kvb3kkMPyMUlEefe?p=preview

Current behavior
All select elements generated with p-dropdown's have the same value for name attribute ('options').

I believe this is the line that causes this:

https://github.com/primefaces/primeng/blob/master/src/app/components/dropdown/dropdown.ts#L24

Expected behavior
The select elements should use the name that was passed into the p-dropdown

Minimal reproduction of the problem with instructions
http://plnkr.co/edit/4Ct8Kvb3kkMPyMUlEefe?p=preview

Click "Log form selects" and you'll see that the select elements all have the same name.

What is the motivation / use case for changing the behavior?
I'm trying to use Prime NG components on a form that is submitted using the default form submit behavior (e.g. action="" and method="" on the form).

Please tell us about your environment:
CentOS, Chrome

  • Angular version: 4.3.2

  • PrimeNG version: 4.2.0

  • Browser: [Chrome ]
  • Language: [TypeScript]

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

@cagataycivici cagataycivici self-assigned this Oct 20, 2017
@cagataycivici cagataycivici added this to the 4.2.3 milestone Oct 20, 2017
@cagataycivici cagataycivici added the Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add label Oct 20, 2017
@cagataycivici cagataycivici changed the title Dropdown accessible select elements do not have name attribute set name property for Dropdown Oct 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Projects
None yet
Development

No branches or pull requests

2 participants