Topic: Issue disabling inputs using FormControl and mdb-form-control
Dave Moniz premium priority asked 3 years ago
Expected behavior
Setting a FormControl
to be disabled
using the recommended method should work
Actual behavior
It doesn't. Additionally, doing it the way recommended in the MDB documentation ( [disabled]="true"
) throws a angular warning
Resources (screenshots, code snippets etc.)
HTML
<mdb-form-control>
<input mdbInput [mdbValidate]="true" id="firstname" name="firstname" formControlName="firstnameControl" type="text" class="form-control">
<label mdbLabel for="firstname" class="form-label">First name</label>
<mdb-error *ngIf="(firstnameControl?.invalid && (firstnameControl?.dirty || firstnameControl?.touched))">This must not be blank</mdb-error>
<mdb-success *ngIf="firstnameControl?.valid && (firstnameControl?.dirty || firstnameControl?.touched)"></mdb-success>
</mdb-form-control>
TS
this.formGroup = new FormGroup({
firstnameControl: new FormControl({
value: this.firstname, disabled: true }, {
validators: [Validators.required], updateOn: 'change'
})
});
using the code (above) does not result in a disabled field, additionally this does not disable the field: this.firstnameControl.disable();
Dave Moniz premium priority answered 3 years ago
Closed
This topic is closed.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Closed
- User: Free
- Premium support: No
- Technology: MDB Angular
- MDB Version: MDB5 1.0.0-beta5
- Device: PC
- Browser: Google Chrome
- OS: Arch Linux
- Provided sample code: No
- Provided link: No
Arkadiusz Idzikowski staff commented 3 years ago
@Dave Moniz We will take a closer look at this and add possibility to disable the control using Angular form control. For now, please use
[disabled]
onmdbInput
, Angular will always suggest to handle disabled state usingFormControl
options, but this warning should not be displayed in production build.