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

MultiSelect: Invisible chips have enabled clear buttons #15479

Closed
szlezakbartosz opened this issue May 7, 2024 · 1 comment
Closed

MultiSelect: Invisible chips have enabled clear buttons #15479

szlezakbartosz opened this issue May 7, 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

@szlezakbartosz
Copy link

Describe the bug

When adding chips to multiselect component, the chips that do not fit the input are still generated (at least some of them). Even though they are invisible, they still have active clear buttons. Because of that it's possible to remove the chip eg. when trying to open the dropdown. It is reproducable in the docs:

bandicam.2024-05-07.13-10-49-096.mp4

Environment

Reproducer

No response

Angular version

17.3.1

PrimeNG version

17.16.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.19.0

Browser(s)

No response

Steps to reproduce the behavior

  1. Open multiselect dropdown
  2. Select multiple items
  3. Inspect the input and look for invisible chip's remove button
  4. Click the invisible button
  5. Chip is removed and item is deselected

Expected behavior

Invisible items should not allow interactions. If the chips need to be generated even though they are not visible, the remove buttons should be disabled.

@szlezakbartosz szlezakbartosz added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 7, 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