Use case for this in core is the "Number of items to index during cron runs" setting in admin/config/search/settings:

It currently allows for a choice between 6 pre-defined values, as shown in the screenshot above. Ideally, we could allow any custom value (grater than 0), and offer these values as suggestions, instead of having them hard-coded.
The HTML5 number field allows that as follows:
<input id="ticketNum" type="number" name="ticketNum" list="defaultNumbers">
<span class="validity"></span>
<datalist id="defaultNumbers">
<option value="10045678">
<option value="103421">
<option value="11111111">
<option value="12345678">
<option value="12999922">
</datalist>
Which makes the <input> field a free-type number field + offers the suggested values in a drop-down in the same field:

Recent comments
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module...
Weekly Meetings July 23rd 2026
If there's some time left in the dev meeting - although it might rather be a topic for the PMC: We have nice documentation and procedures, how to provide projects in backdrop-contrib space...
Weekly Meetings July 23rd 2026
The need for a clear AI policy is growing. Please can this be a priority.
Weekly Meetings July 23rd 2026