You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report => Search github for a similar issue or PR before submitting
[X] 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 a p-dropdown, select tag doesn't have an attribute "id"
Expected behavior
When using a p-dropwn, select tag have an "id" => <select [attr.id]="selectId"...
InputId cannot be used because its' already used for the hidden input.
What is the motivation / use case for changing the behavior?
We use some automatic test (like Robot Framework with selenium) and there's some libs that can extract the options list for a select but we have to put in input an id.
Then it's a best pratice that all the "input tag" (select is an "input") can have an id
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Current behavior
When using a p-dropdown, select tag doesn't have an attribute "id"
Expected behavior
When using a p-dropwn, select tag have an "id" =>
<select [attr.id]="selectId"...
InputId cannot be used because its' already used for the hidden input.
What is the motivation / use case for changing the behavior?
We use some automatic test (like Robot Framework with selenium) and there's some libs that can extract the options list for a select but we have to put in input an id.
Then it's a best pratice that all the "input tag" (select is an "input") can have an id
The text was updated successfully, but these errors were encountered: