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

Reactive Forms issue with p-InputNumber and updateOn:'blur'. Issue is also there for Template Driven forms when explicitly using [ngModelOptions]="{ updateOn: 'blur' }" #14842

Closed
dbenedettoWithum opened this issue Feb 19, 2024 · 3 comments
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@dbenedettoWithum
Copy link

dbenedettoWithum commented Feb 19, 2024

Describe the bug

When using reactive forms with primeng version 15.3.0, we noticed the valueChanges property of the reactive form gets triggered as soon as the user inputs a value in the input field even though the updateOn property is set on the control.
value: new FormControl(1234, { updateOn: 'blur' }),

Expectations: If updateOn blur is set, the valuechanges should not get triggered till the user blurs the control.

We also noticed the issue when using Template Driven Forms and explicitly setting [ngModelOptions]="{ updateOn: 'blur' }".

Environment

N/A

Reproducer

No response

Angular version

15.1.5

PrimeNG version

15.3.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.17.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@dbenedettoWithum dbenedettoWithum added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 19, 2024
@dbenedettoWithum dbenedettoWithum changed the title Reactive Forms issue with p-InputNumber and udpateOn:'blur' Reactive Forms issue with p-InputNumber and updateOn:'blur'. Issue is also visible for Template Driven forms when explicitly using [ngModelOptions]="{ updateOn: 'blur' }" Feb 19, 2024
@dbenedettoWithum dbenedettoWithum changed the title Reactive Forms issue with p-InputNumber and updateOn:'blur'. Issue is also visible for Template Driven forms when explicitly using [ngModelOptions]="{ updateOn: 'blur' }" Reactive Forms issue with p-InputNumber and updateOn:'blur'. Issue is also there for Template Driven forms when explicitly using [ngModelOptions]="{ updateOn: 'blur' }" Feb 19, 2024
@dbenedettoWithum
Copy link
Author

Found the same issue referenced here in : #12915 and #12673

@mehmetcetin01140 mehmetcetin01140 added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Feb 26, 2024
Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Jun 30, 2024
Copy link

github-actions bot commented Jul 7, 2024

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

2 participants