bug(MatChipInput): MatChipInput does not set `mat-form-field-disabled` on MatFormField wrapper when being disabled

[clamli]

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

No response

Description

When a MatChipInput is disabled, it does not set mat-form-field-disabled CSS class on its MatFormField wrapper like it does for MatInput.

Reproduction

StackBlitz link: https://stackblitz.com/edit/xcgzeewq?file=src%2Fexample%2Fchips-input-example.html
Steps to reproduce:

1. There are one disabled MatChipInput and one disabled MatInput in the example
2. The form field wrapper of the MatInput has mat-form-field-disabled CSS class, while the form field wrapper of the MatChipInput does not

Expected Behavior

Both of the form field should set mat-form-field-disabled CSS class as the input is disabled.

Actual Behavior

The form field wrapper of the MatInput has mat-form-field-disabled CSS class, while the form field wrapper of the MatChipInput does not

Environment

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

[crisbeto]

This is most likely because mat-chip-grid gets picked up as the form field control, not the input. You can set the disabled state on mat-chip-grid instead.

[clamli]

Our use case is that we want the chip input to be focusable when it is disabled so we can attach a disabled tooltip. We set disabled and disabledInteractive on the chip input, expecting the chip input to be showed in a disabled styling while still remain focusable.

Setting disabled on the chip grid will make the entire chip input not focusable even if I set disabledInteractive to true on the input.