bug(MatChipOption): Unable to disable individual mat-chip-option when used inside a form tag and with template-driven forms

[gremlin896]

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

[disabled] used on a mat-chip-option that is part of a mat-chip-listbox is ignored when used with template-driven forms and is there is a parent form tag used.

Reproduction

StackBlitz link: https://stackblitz.com/edit/84akr3-apxcdy

Two identical examples, but the first example is enclosed within <form>

Expected Behavior

In the first example, the first option should be disabled. As it is in the second example

Actual Behavior

In the first example, the first option is not disabled.

Environment

Angular CLI: 19.0.0-next.2
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 19.0.0-next.2
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, localize, material, material-moment-adapter
... platform-browser, platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.1900.0-next.2
@angular-devkit/build-angular 19.0.0-next.2
@angular-devkit/core 19.0.0-next.2
@angular-devkit/schematics 19.0.0-next.2
@schematics/angular 19.0.0-next.2
rxjs 7.4.0
typescript 5.5.4
zone.js 0.15.0

[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.}