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: TriStateCheckBox ngModelChange doesn't fire when ngModel binding set programmatically #14019

Closed
lwestfall opened this issue Nov 3, 2023 · 1 comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@lwestfall
Copy link
Contributor

Describe the bug

TriStateCheckBox's ngModelChange doesn't emit an event when ngModel binding set programmatically

Environment

N/A

Reproducer

https://stackblitz.com/edit/n6ctbj?file=src%2Fapp%2Fdemo%2Ftri-state-checkbox-basic-demo.html

Angular version

16.2.0

PrimeNG version

16.7.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

latest

Browser(s)

No response

Steps to reproduce the behavior

  1. See stackblitz: https://stackblitz.com/edit/n6ctbj?file=src%2Fapp%2Fdemo%2Ftri-state-checkbox-basic-demo.html
  2. Click one of the three buttons. These programmatically set the value that's bound to the TriStateCheckBox model
  3. Note no message appears.
  4. Click the checkbox. Message appears.

Expected behavior

In this stackblitz, I expect a message when one of the buttons is pressed (same behavior as when the checkbox itself is clicked).

@lwestfall lwestfall 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 3, 2023
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 Dec 16, 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 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