You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a wrapper component which is implementing ControlValueAcessor, and I'm using the setDisabledState from the primeng input. It's not working correctly when I start the form control as disabled. The input appears to be disabled, but once I click on it I'm able to edit the value, and then the field gets disabled for good.
Environment
I use a windows 11 laptop. Angular 17.3.5, PrimeNG 17.12.0 and node v20.10.0
Describe the bug
I have a wrapper component which is implementing ControlValueAcessor, and I'm using the setDisabledState from the primeng input. It's not working correctly when I start the form control as disabled. The input appears to be disabled, but once I click on it I'm able to edit the value, and then the field gets disabled for good.
Environment
I use a windows 11 laptop. Angular 17.3.5, PrimeNG 17.12.0 and node v20.10.0
Reproducer
https://stackblitz.com/edit/github-daas27-pb8btj?file=src%2Fapp%2Fapp.component.ts
Angular version
17.3.5
PrimeNG version
17.12.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.10.0
Browser(s)
No response
Steps to reproduce the behavior
Expected behavior
Component is disabled from the beginning and stays disabled until we enable it in the ReactiveForm
The text was updated successfully, but these errors were encountered: