You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
For anybody struggling with names on radio buttons and checkboxes #331
the id name was originally implemented to prevent name collisions but i think we can remove this restriction and add a tooltip informing the form editor if an element already exists with the same name.
This still applies in v5: radio and checkbox groups take their name from attrs.id (or the field id) and ignore a name attribute. It's the same root cause as #270 and #220, and the planned fix covers all three. Option inputs will use attrs.name when it's set, then attrs.id, then the field id, so the attrs.id workaround above keeps working. One heads-up for later: a group that already has a name saved will start submitting under that name instead of f-<id>.
Activity
aptvaltechtest commentedon Sep 28, 2022
{ tag: 'input', config: { label: 'Checkbox Group', editorLabel: 'Checkbox Group', disabledAttrs: ['name'], lockedAttrs: ['name','required','className'], }, meta: { group: 'common', id: 'chkbox', icon: 'checkbox', }, options: [ {label: 'Option 1', value: 'opt1', selected: true} ], attrs: { id: '', className: '', type: 'checkbox', required: true, }, },kevinchappell commentedon Nov 19, 2024
the id name was originally implemented to prevent name collisions but i think we can remove this restriction and add a tooltip informing the form editor if an element already exists with the same name.
kevinchappell commentedon Sep 25, 2026
This still applies in v5: radio and checkbox groups take their
namefromattrs.id(or the field id) and ignore anameattribute. It's the same root cause as #270 and #220, and the planned fix covers all three. Option inputs will useattrs.namewhen it's set, thenattrs.id, then the field id, so theattrs.idworkaround above keeps working. One heads-up for later: a group that already has anamesaved will start submitting under that name instead off-<id>.chore(release): 5.2.2 [skip ci]
kevinchappell commentedon Sep 26, 2026
🎉 This issue has been resolved in version 5.3.3 🎉
The release is available on:
Your semantic-release bot 📦🚀
fix(edit-panel): compare field names verbatim, as the renderer submit…
chore(release): 5.10.0 [skip ci]