This bug seems to be directly related to the same problems I experienced with the multiselect field in the latest v4-alpha-release.
Description
The tag field ignores the blueprint-setting accept: options and always comes up with a misleading create-option whenever a search for a non-existing option is performed. (This happens with both static and dynamic options / using the create-feature doesn't do anything at all.)
The tag field cuts of options with long titles due to its limited width.
Expected behavior
The tag field should not contain a create-option if the blueprint contains accept: options.
The tag field should not cut off options as long as there is enough space left to show them properly.
This bug seems to be directly related to the same problems I experienced with the multiselect field in the latest v4-alpha-release.
Description
accept: options
and always comes up with a misleading create-option whenever a search for a non-existing option is performed. (This happens with both static and dynamic options / using the create-feature doesn't do anything at all.)Expected behavior
accept: options
.Screenshots
To reproduce
accept: options
-setting to the blueprint.Your setup
Kirby Version: 4.0.0-alpha.7.