The HTML for that input is a function of the time when the new forum was built, when there wasn't a standardised way to say "Number keyboard please, browser" and Apple suggested using the regex in the pattern attribute.
<input type="text" min="1" value="817" max="817" step="1" pattern="\d*" title="Enter the page number to jump to" class="form-control">
I've seen some discussion that this may trigger unexpected behaviour in combination with some personal setting, VPN or something else.
Nowadays you would use the tel input type. (or the inputmode attribute but Safari - naturally - doesn't support that)
<input type="tel" min="1" value="817" max="817" step="1" title="Enter the page number to jump to" class="form-control">
Maybe that simple change would solve the problem?
I cannot reproduce the bug so no point me making a pull request but that's what I would try changing first if I could actually test it.
There would need to be manual validation of the min and max values as they don't actually apply to tel inputs.
The HTML for that input is a function of the time when the new forum was built, when there wasn't a standardised way to say "Number keyboard please, browser" and Apple suggested using the regex in the
pattern
attribute.I've seen some discussion that this may trigger unexpected behaviour in combination with some personal setting, VPN or something else.
Nowadays you would use the
tel
input type. (or theinputmode
attribute but Safari - naturally - doesn't support that)Maybe that simple change would solve the problem?
I cannot reproduce the bug so no point me making a pull request but that's what I would try changing first if I could actually test it.
There would need to be manual validation of the min and max values as they don't actually apply to
tel
inputs.