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

p-autoComplete | showClear property not clear the ngModel value #12729

Closed
pjhifo opened this issue Mar 9, 2023 · 2 comments
Closed

p-autoComplete | showClear property not clear the ngModel value #12729

pjhifo opened this issue Mar 9, 2023 · 2 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@pjhifo
Copy link

pjhifo commented Mar 9, 2023

Describe the bug

I enabled the showClear property on my p-autoComplete component, but when I clicked the × button, the value on his control was cleared, but the ngModel's value remained.
I have tried to upgrade the version, but I have upgraded to the latest version and still have this problem.
I tried StackBlitz on the site and also had this problem.

Environment

Angular version
15.2.2

PrimeNG version
15.2.0

Reproducer

No response

Angular version

15.2.2

PrimeNG version

15.2.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.13.2

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@pjhifo pjhifo added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 9, 2023
@pjhifo pjhifo changed the title Component: Title p-autoComplete | showClear property not clear the ngModel value Mar 10, 2023
@flortsch
Copy link

flortsch commented Dec 16, 2023

I am on PrimeNG 15.4.1 and Angular 15.2.10. Experiencing the same issue. As a workaround, I am using the onClear hook to reset the ngModel myself.

@mehmetcetin01140
Copy link
Contributor

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

3 participants