Current Behavior

The allowCustomValue property on the Combobox seems to have no affect. Usually when allowing custom values, a return key press or comma will communicate that "This is a new value I want to save as a selected value. However, when this property is set to true, nothing

Here are a few examples of other Combobox / AutoCompletes that support values not in the drop down list:

• Look at the "Free Solo" sample. When I hit enter, the text I entered turns into a chip.
• Look at the Autocomplete sample. An enter key or comma both add a new value to the list.

The current Combobox does not support this functionality.

Expected Behavior

When allowCustomValue is set to true, I expect the enter key--or possibly the comma--to treat the text I entered as if it were a new value.

Steps To Reproduce

1. Create a Combobox with the allowCustomValue property set to true
2. Type a value not in the drop down
3. Hit the enter key, or comma, and the value you entered is never added to 'values' as a selected value.

Link to Reproduction / Stackblitz

No response

Environment Information

All my testing was on the latest version of Chrome; with Svelte 5, Tailwind 4.

More Information

No response