bug(Form Controls): FormControl disabled state now overrides the template state

[zakhenry]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

14

Description

This is a regression, before the [disabled] attribute of a form element (radio, toggle etc) would take precedence, but now this attribute appears to be ignored entirely if the component is bound to a form control

Before:
https://stackblitz.com/edit/angular-pw8j5w?file=src/app/radio-ng-model-example.html

After:
https://stackblitz.com/edit/angular-tomdov?file=src/app/radio-ng-model-example.html

Note the content of these demos are identical other than the different bootstrapped version, one is showing the control as disabled (v14) and the other as enabled (v15)

Reproduction

Steps to reproduce:

1. Set up a form component with a [disabled]="true" attribute
2. Attach a formControl via [formControl] with no disabled state set (the default)
3. Inspect the ui

Expected Behavior

Form component should be disabled

Actual Behavior

Form component is not disabled

Environment

• Angular: 15.0.0
• CDK/Material: 15.0.3
• Browser(s): Chrome
• Operating System (e.g. Windows, macOS, Ubuntu): macOS

[EmmanuelRoux]

@zakhenry Probably because of this (breaking) change from @angular/forms v15 ?
angular/angular@6ab382e

But [disabled] should not be bind from template with reactive forms

[crisbeto]

@EmmanuelRoux is correct. We implement the ControlValueAccessor and leave it up to the forms module to notify the component when it should be disabled.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}