Skip to content

Conversation

crisbeto
Copy link
Member

The chip set has been set up in a way where it syncs its state to the chips, instead of the other way around which we follow in other components. This means that if its disabled state changes later, it can ovewrite the state that the user explicitly set on the chip.

These changes make the logic a bit more robust by writing to a different field.

Fixes #29783.

The chip set has been set up in a way where it syncs its state to the chips, instead of the other way around which we follow in other components. This means that if its `disabled` state changes later, it can ovewrite the state that the user explicitly set on the chip.

These changes make the logic a bit more robust by writing to a different field.

Fixes angular#29783.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Sep 27, 2024
@crisbeto crisbeto requested a review from a team as a code owner September 27, 2024 07:01
@crisbeto crisbeto requested review from amysorto and mmalerba and removed request for a team September 27, 2024 07:01
@crisbeto crisbeto removed the request for review from amysorto September 30, 2024 17:45
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 30, 2024
@crisbeto crisbeto merged commit 86ebb9b into angular:main Sep 30, 2024
23 of 25 checks passed
crisbeto added a commit that referenced this pull request Sep 30, 2024
The chip set has been set up in a way where it syncs its state to the chips, instead of the other way around which we follow in other components. This means that if its `disabled` state changes later, it can ovewrite the state that the user explicitly set on the chip.

These changes make the logic a bit more robust by writing to a different field.

Fixes #29783.

(cherry picked from commit 86ebb9b)
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

2 participants