Bug description
When a Bard field contains two or more sets of the same set type, and that set type has a radio field, clicking directly on an option's label text — as opposed to clicking the radio input itself — can select/change the option in a different set instance of the same type, not the one you clicked in. If a set of a different type is between them the value shown doesn't reliably match the option you clicked (e.g. clicking "Option 1" can result in "Option 2" appearing selected in another set).
Most reliably reproduced right after inserting a new set of the same type as an existing one, on a brand-new, unsaved entry. Clicking the radio input circle itself (rather than the label) does not trigger the bug.
How to reproduce
Create a Bard field with a set type that includes a radio field with a few options:
fields:
- handle: section_type
field:
type: radio
inline: true
options:
- { key: about, value: About }
- { key: feature, value: Feature }
- { key: cta, value: CTA }
Create a new entry using a blueprint with that Bard field.
Add a set of that type to the Bard field. Pick an option (e.g. "About").
Add a second set of the same type directly after it.
In the second set, click the label text of a different radio option (e.g. "Feature") — not the radio dot itself.
Expected behavior:
Only the set you clicked in should update, to the option you actually clicked.
Logs
Environment
Environment
Laravel Version: 12.64.0
PHP Version: 8.3.30
Composer Version: -
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: Europe/London
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: memcached
Database: mysql
Logs: stack / single
Mail: log
Queue: database
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 4
License Key: Not set
Sites: 6
Stache Watcher: Disabled
Static Caching: full
Version: 6.29.0 PRO
Statamic Addons
aerni/font-awesome: 4.0.1
statamic/eloquent-driver: 5.10.0
statamic/importer: 2.2.0
statamic/seo-pro: 7.13.3
Statamic Eloquent Driver
Addon Settings: eloquent
Asset Containers: eloquent
Assets: eloquent
Blueprints: eloquent
Collection Trees: eloquent
Collections: eloquent
Entries: eloquent
Fieldsets: eloquent
Form Submissions: eloquent
Forms: eloquent
Global Sets: eloquent
Global Variables: eloquent
Navigation Trees: eloquent
Navigations: eloquent
Revisions: eloquent
Sites: eloquent
Taxonomies: eloquent
Terms: eloquent
Tokens: eloquent
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
Bug description
When a Bard field contains two or more sets of the same set type, and that set type has a radio field, clicking directly on an option's label text — as opposed to clicking the radio input itself — can select/change the option in a different set instance of the same type, not the one you clicked in. If a set of a different type is between them the value shown doesn't reliably match the option you clicked (e.g. clicking "Option 1" can result in "Option 2" appearing selected in another set).
Most reliably reproduced right after inserting a new set of the same type as an existing one, on a brand-new, unsaved entry. Clicking the radio input circle itself (rather than the label) does not trigger the bug.
How to reproduce
Create a Bard field with a set type that includes a radio field with a few options:
Create a new entry using a blueprint with that Bard field.
Add a set of that type to the Bard field. Pick an option (e.g. "About").
Add a second set of the same type directly after it.
In the second set, click the label text of a different radio option (e.g. "Feature") — not the radio dot itself.
Expected behavior:
Only the set you clicked in should update, to the option you actually clicked.
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response