Description
Calling control.disable() on a reactive FormControl bound to an igx-simple-combo (or igx-combo) flips the combo's visual state to IgxInputState.INVALID (red error border) — even though a disabled control should never render as invalid. This happens whenever the control has been touched or is dirty.
Framework
Angular
Angular Version
21.2.10
Ignite UI for Angular Version
21.2.0
Component / Area
Combo / Simple Combo
Browser
Chrome, Firefox, Edge, Safari
Operating System
Windows
Command Not Working
Steps to Reproduce
- Bind an igx-simple-combo to a reactive FormControl.
- Select a value.
- Call control.disable() from code.
Actual Result
The combo renders with the red INVALID border.
Expected Result
The combo renders in its neutral/disabled state. The form control's status is DISABLED, it is not invalid.
Reproduction URL
https://stackblitz.com/edit/dzpzeigy
Attachments

Description
Calling
control.disable()on a reactive FormControl bound to an igx-simple-combo (or igx-combo) flips the combo's visual state toIgxInputState.INVALID(red error border) — even though a disabled control should never render as invalid. This happens whenever the control has been touched or is dirty.Framework
Angular
Angular Version
21.2.10
Ignite UI for Angular Version
21.2.0
Component / Area
Combo / Simple Combo
Browser
Chrome, Firefox, Edge, Safari
Operating System
Windows
Command Not Working
Steps to Reproduce
Actual Result
The combo renders with the red INVALID border.
Expected Result
The combo renders in its neutral/disabled state. The form control's status is DISABLED, it is not invalid.
Reproduction URL
https://stackblitz.com/edit/dzpzeigy
Attachments