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

inputSwitch dynamic disabled cause ExpressionChangedAfterItHasBeenCheckedError #14126

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

Comments

@lufo88ita
Copy link

Describe the bug

If I use a variable to set disabled in InputSwitch
https://primeng.org/inputswitch

and change the value from false to true in console it show
ExpressionChangedAfterItHasBeenCheckedError

Environment

OS: Windows 10
Angular 16.2
Primeng: 16.7.2
But it happens also in
primeng 14.2.3
angular 14.2
And I suppose in primeng 15 also.

Reproducer

https://stackblitz.com/edit/ich5kf-cksjho?file=src%2Fapp%2Fdemo%2Finput-switch-disabled-demo.html

Angular version

16.2

PrimeNG version

16.7.2

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.20.2

Browser(s)

Chrome 119.0.6045.159

Steps to reproduce the behavior

  1. Open the stackblitz example
  2. Click on the inputswitch (the example disabled the input switch for 2 seconds)
  3. Watch in the console the error

Expected behavior

No error print in the console

@lufo88ita lufo88ita 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
@mertsincan
Copy link
Member

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 reopen the issue so we can include it in our roadmap?
Please don't forget to add your feedback as a comment after reopening the issue. These will be taken into account by us and will contribute to the development of this feature. 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