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: p-chips form enable disable #14130

Closed
ericvaroto opened this issue Nov 15, 2023 · 1 comment
Closed

Component: p-chips form enable disable #14130

ericvaroto opened this issue Nov 15, 2023 · 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

@ericvaroto
Copy link

Describe the bug

Hello,
I'm having a problem with my chips component inside a Form (FormGroup).
When I enable my form after disable, the input text keep disabled, blocking user type text

My Form instantiate example:
this.form = new FormGroup({listTag: new FormControl<string[] | null>(null)});

My Enable/Disable method:

this.form.disable();
this.form.enable();

My HTML with Forms and Chips

<form [formGroup]="form" class="card">
    <div class="flex flex-column gap-2 p-fluid">
      <p-chips
        [separator]="tagsSeparatorExp"
        [allowDuplicate]="false"
        [showClear]="true"
        pKeyFilter="alphanum"
        placeholder="Tecle: a, b, c"
        formControlName="listTag"
      />
    </div>
</form>

Environment

Production: Angular v16

Reproducer

No response

Angular version

16.2.10

PrimeNG version

16.7.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.9.0

Browser(s)

No response

Steps to reproduce the behavior

  1. Create a Chips inside Angular Forms
  2. When component initializes (ngOnInit), disable the Form Group
  3. After some time, enable it again
  4. You will see that the input text is disabled

Expected behavior

No response

@ericvaroto ericvaroto 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 15, 2023
@ericvaroto
Copy link
Author

Problem was fixed in issue #14062 and released in 16.8.0.

Closing my issue...
Thanks!

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