Skip to content

ChipField: Respect parent form Disabled and ReadOnly state - #653

Open
redgp0g wants to merge 1 commit into
CodeBeamOrg:devfrom
redgp0g:fix/issue-270-chip-field-on-form-disabled
Open

redgp0g wants to merge 1 commit into
CodeBeamOrg:devfrom
redgp0g:fix/issue-270-chip-field-on-form-disabled

Conversation

@redgp0g

@redgp0g redgp0g commented Nov 1, 2026

Copy link
Copy Markdown

Chips used the component's own Disabled parameter, and Closed() checked Disabled/ReadOnly directly, so chips stayed enabled and removable inside a read-only MudForm (I don't know exactly why, but in the disabled MudForm was working in my test). So I changed to GetDisabledState() and GetReadOnlyState() so the cascaded form state is honored.

Fixes #270

Before:

Gravacao.de.Tela.2026-11-01.203646.mp4

After:

Gravacao.de.Tela.2026-11-01.203939.mp4

Chips used the component's own Disabled parameter, and Closed() checked
Disabled/ReadOnly directly, so chips stayed enabled and removable inside
a disabled or read-only MudForm. Use GetDisabledState() and
GetReadOnlyState() so the cascaded form state is honored.

Fixes CodeBeamOrg#270

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MudChipField does not respect MudForm.Disabled

1 participant