Problem Statement
In the UVE quick-edit form, all `p-radioButton` and `p-checkbox` inputs across different content type fields share the same browser group because the `[name]` binding is missing. Selecting an option in one field deselects or affects options in another — they behave as a single group instead of independent field controls.
Affected file: `libs/portlets/edit-ema/portlet/src/lib/edit-ema-editor/components/dot-uve-contentlet-quick-edit/dot-uve-contentlet-quick-edit.component.html`
Steps to Reproduce
- Open the Universal Visual Editor (UVE)
- Click a contentlet that has multiple Radio or Checkbox fields
- The quick-edit panel opens on the right
- Select a radio button option in one field — it deselects the selection in another radio field
- Same behavior for checkboxes across different fields
Root Cause
PrimeNG's `p-radioButton` and `p-checkbox` require an explicit `[name]` binding to scope each group. Without it, all instances rendered in the `@for` loop share the same internal name and the browser groups them all together.
Acceptance Criteria
dotCMS Version
Latest from main branch
Severity
Medium - Some functionality impacted
Problem Statement
In the UVE quick-edit form, all `p-radioButton` and `p-checkbox` inputs across different content type fields share the same browser group because the `[name]` binding is missing. Selecting an option in one field deselects or affects options in another — they behave as a single group instead of independent field controls.
Affected file: `libs/portlets/edit-ema/portlet/src/lib/edit-ema-editor/components/dot-uve-contentlet-quick-edit/dot-uve-contentlet-quick-edit.component.html`
Steps to Reproduce
Root Cause
PrimeNG's `p-radioButton` and `p-checkbox` require an explicit `[name]` binding to scope each group. Without it, all instances rendered in the `@for` loop share the same internal name and the browser groups them all together.
Acceptance Criteria
dotCMS Version
Latest from main branch
Severity
Medium - Some functionality impacted