| fooishbar | |
| Jul 22 2016, 6:22 PM |
| F1734187: Screen Shot 2016-07-23 at 1.24.01 PM.png | |
| Jul 23 2016, 8:27 PM |
| F1734191: Screen Shot 2016-07-23 at 1.16.06 PM.png | |
| Jul 23 2016, 8:27 PM |
| F1734185: Screen Shot 2016-07-23 at 1.22.56 PM.png | |
| Jul 23 2016, 8:27 PM |
| F1732470: IMG_4904.PNG | |
| Jul 22 2016, 6:22 PM |
Applies to w29 stable, and the version currently running on this install.
Configure TOTP 2FA for your user account.
Log in on a mobile browser.
TOTP challenge prompt displays the full keyboard, not the numeric-only version, as the field is not fully annotated in the DOM.
It would be nice if this were the case.
Offhand, do you know if <input type="number" /> has the desired behavior on your device?
On iPhone Simulator, the behavior of <input type="number" /> appears to be "draw the keyboard for 1 frame and then immediately hide it".
On iOS 9.2 in the simulator, <input type="number" /> gives you this keyboard:
This also makes desktop Safari render the control with a weird little increment sub-control, which is useless in this context (note "" and "" buttons inside the control on the right):
With <input type="text" pattern="\d*" />, I get the desired keyboard:
On desktop Safari on OSX, this appears to have no special behavior (I can type letters into the control).
On desktop Chrome on OSX, this also appears to have no special behavior.
On desktop Firefox on OSX, this also appears to have no special behavior.
I don't have a convenient way to test any Android mobile devices locally.
D16323 uses <input type="text" pattern="\d*" />, which appears to have the best behavior.
@epriestley Missed a spot: D16325
Beyond that, it does exactly the right thing on real iOS. Thanks!