Bug description
Options in Checkboxes fields may have a space in their keys.
But it is not possible to type a space into the Default value field.
The only way to bypass this restriction is to paste the values into the field, which is how I managed to make the screenshot below. Saving is possible after doing so.

On a related note, there is no auto-completion for the default values field, meaning a non-existing key could be typed in there. I am unsure what functionality that allows.
How to reproduce
- Add a checkboxes field in any blueprint
- Add a key/label pair where the key has a space inside it (this step does not matter but if you do it, at least, you will rule out the possibility the space wasn't accepted because it does not match an existing key).
- Try to type a default value with a space inside it
Logs
Environment
Environment
Laravel Version: 12.53.0
PHP Version: 8.3.6
Composer Version: 2.9.2
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Livewire
Livewire: v4.2.1
Statamic
Addons: 3
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.8.0 Solo
Statamic Addons
allyoullneed/inline-bard-components: dev-main
allyoullneed/statamic-forms: dev-main
alt-design/alt-seo: 1.4.0
Installation
Fresh statamic/statamic site via CLI
Additional details
I tested pasting values with in a Form Blueprint and fields are correctly rendered in the form.
Test was done with a Statamic addon I will soon publish (wish me luck) but I have no reason to believe it may misbehave if using e.g. dynamic rendering of fields as values look well-formed.
I have not tested it in a collection blueprint but I suppose it works just as well.
AFAICT, default values in Radios fieldtype accept typing spaces, as they should.
Bug description
Options in
Checkboxesfields may have a space in their keys.But it is not possible to type a space into the Default value field.

The only way to bypass this restriction is to paste the values into the field, which is how I managed to make the screenshot below. Saving is possible after doing so.
On a related note, there is no auto-completion for the default values field, meaning a non-existing key could be typed in there. I am unsure what functionality that allows.
How to reproduce
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
I tested pasting values with in a Form Blueprint and fields are correctly rendered in the form.
Test was done with a Statamic addon I will soon publish (wish me luck) but I have no reason to believe it may misbehave if using e.g. dynamic rendering of fields as values look well-formed.
I have not tested it in a collection blueprint but I suppose it works just as well.
AFAICT, default values in Radios fieldtype accept typing spaces, as they should.