Overview
In the Shoe Icon Library, the two dropdown fields – Color and Size – the second option (the one immediately after "None") is not visible(see attached screenshot).
The first option ("None") appears as expected, but the value right below it is missing from both dropdowns.


Steps to Reproduce:
- Navigate to the Shoe Icon Library interface.
- Check the Color dropdown from the settings, the second select value is not visible, but can be selected.
- Check the Size dropdown, the second select value is not visible, but can be selected.
While resolving the issue, we need to take care that default value didn't got changed.
Proposed resolution
User interface changes
| Comment | File | Size | Author |
|---|---|---|---|
| color_dropdown.png | 36.85 KB | jatingupta40 | |
| ADSASD.png | 46.61 KB | jatingupta40 |
Issue fork experience_builder-3523860
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
jatingupta40 commentedComment #4
wim leersComment #5
penyaskitoThanks for jumping on this, @jatingupta40!
This is technically correct, because it's what the component defined. Fixing it in our components won't prevent other components from outside of XB to do that.
In #3516602: SDC `enum` props should have human-readable labels: use `meta:enum` (and potentially in core #3493070: SDC `enum` props should have translatable labels: use `meta:enum`) we will allow to provide labels for every enum value, including those enum values that are the empty string.
We still need to figure out if there's any technical reason for not allowing an empty value, which I'm not sure it does exist anymore.
If it does, we would need to update
SingleDirectoryComponent::checkRequirements()to detect and disallow components that provide those.Comment #6
wim leersI think this is a duplicate of #3503087: Disallow SDCs with `type: string, enum: …` with an empty string listed to convey optionality: the prop should then just be optional.
Comment #7
jatingupta40 commentedThanks @penyaskito for clarifying this so well.
Closing this ticket as it is a duplicate of - https://www.drupal.org/project/experience_builder/issues/3503087
Comment #8
jatingupta40 commented