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

Chips: Component is always disabled if not set to bind to a model #14050

Closed
timandella opened this issue Nov 7, 2023 · 1 comment
Closed
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@timandella
Copy link

timandella commented Nov 7, 2023

Describe the bug

In previous versions of PrimeNG (16.6.0 and earlier), it was possible to create a Chips component without explicitly binding to a model value (i.e. when reactive forms are used)

    <p-chips 
        separator="," 
        placeholder="Hint: a, b, c"></p-chips>

However, in 16.7.1 (and 16.7.0), this now results in the component being disabled, and the user unable to type anything in the control. It is only if you add the [(ngModel)] binding does the control become enabled.

In previous versions, omitting [(ngModel)] left the control as enabled, and the user could still type into the control

Environment

Windows

Reproducer

https://stackblitz.com/edit/7cfcg5?file=src%2Fapp%2Fdemo%2Fchips-comma-seperator-demo.html

Angular version

16.2.12

PrimeNG version

16.7.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.16.1

Browser(s)

Edge

Steps to reproduce the behavior

  1. Set up a p-Chips element on an html page, without [(ngMode)] being specified
  2. Run your app, and attempt to type into the control

Expected behavior

Control is enabled, and user can type in it to create new chips

@timandella timandella added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 7, 2023
@timandella timandella closed this as not planned Won't fix, can't repro, duplicate, stale Nov 10, 2023
@timandella
Copy link
Author

Duplicate of #14062

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

1 participant