- Notifications
You must be signed in to change notification settings - Fork246
Open
Description
Version
10.0.0
Environment
public library
Reproduction link
https://stackblitz.com/edit/angular-lnnrzplq?file=src%2Fapp%2Fapp.component.ts
(reactive + template-driven form using<InputItem>
)
Steps to reproduce
- Initialize a form with InputItem components using either [formControl], formControlName, or [(ngModel)] and set them to disabled: true
- Add a button that calls form.enable() or changes [disabled] to false
- Click the “Enable Form” button
What is expected?
Input fields become interactive — the user can focus and enter values. The numeric keyboard is displayed automatically after focus.
Labels and UI reflect the enabled state.
What is actually happening?
The label appears enabled (visually), but the underlying input remains disabled and does not allow interaction. No keyboard invoked.
This happens regardless of form binding strategy (formControlName, [formControl], or [(ngModel)]).
It seems the support of this behavior incustom-input
component might be missing.
Other?
- Confirmed on Chrome, Firefox, and Safari
- Angular form control status changes correctly (confirmed via console.log), but the view does not reflect it
- Tested also with manual ChangeDetectorRef and [disabled]="form.get('control')?.disabled" — no success
- This affects dynamic form state management, which is critical for Angular reactive forms usage
Metadata
Metadata
Assignees
Labels
No labels