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: multiselect and dropdown #15268

Closed
FelixTwoli opened this issue Apr 13, 2024 · 1 comment
Closed

Component: multiselect and dropdown #15268

FelixTwoli opened this issue Apr 13, 2024 · 1 comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@FelixTwoli
Copy link

FelixTwoli commented Apr 13, 2024

Describe the bug

Incorrect use of
The label's for attribute does not match any element id, leading to an error in the browser console. This could impact form autofill and accessibility tools.

Environment

Development, staging, and production environments

Reproducer

No response

Angular version

17.3.1

PrimeNG version

17.10.0

Build / Runtime

Angular CLI App

Language

ALL

Node version (for AoT issues node --version)

v20.11.0

Browser(s)

No response

Steps to reproduce the behavior

  1. Use the dropdown or multi-select component in the PrimeNG UI library.
  2. Specify a <label> with a for attribute that does not correspond to any form field id.
  3. Observe the browser console for the error message mentioned.

Expected behavior

The for attribute of the label should reference the correct id of the associated form field for proper functionality and accessibility.

@FelixTwoli FelixTwoli added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Apr 13, 2024
@FelixTwoli FelixTwoli changed the title Incorrect use of <label for=FORM_ELEMENT> Component: multiselect and dropdown Apr 13, 2024
@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 open a new issue so we can include it in our roadmap?

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

No branches or pull requests

2 participants