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:
GitHub Issue #:
5285
Recent comments
Thanks, but that makes no difference. I enter Today as the end, Apply, it ignores it, and I still have just the one date selector.
Between Dates Views Filter not functioning as expected
But when setting End Date, and relative of -0 days or -1 days... Instead of "-0 days" use today and instead of -1 days use yesterday. Find some background re relative...
Between Dates Views Filter not functioning as expected
Worth mentioning as it was in zulip chat by @yorkshirepudding I just tested and the two work together without issue as long as you don't use the "Exclude comments from Content...
Search does not include comments