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
Thanks!! Easiest for me to just give permission for anon users to see the admin theme. That worked. It's just for this one page.
Link field in a Content Type is malformed for annonymous user- Permission issue?
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme. By default, such users won't have permissions to see the...
Link field in a Content Type is malformed for annonymous user- Permission issue?
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS