This advice is incorrect to recommend using type="number". On a desktop, trackpad and mousewheel scrolling while the pointer is hovering over and/or focus is within a type="number" field will alter the number within it, resulting in undetected data errors as digits off-by-one without user awareness.
I think this may have been the result of banking malware (e.g. Zeus back in the day) which was hooking OS calls to capture keyboard input and steal passwords.
I'm not sure whether the on-screen keyboards would be vulnerable in other ways though.
I have had to use a online banking site (from a very, very big global corporate bank) which implemented a keyboard in the (Desktop) browser which you had to click each letter with a mouse to type out your password (in the name of security, presumably).
Indeed BNP Paris does that for the Pin number, so it's only numbers you have to type.
It has been there or a long time, so I kinda consider it a remnant of the old battle against keylogger, since the number position changes.
It does seem outdated now, and I'm unsure if it's still useful compared to all the other possible checks they could implement.
It's not my PIN number, it's used as a password to access on-line banking services. But I agree that it look like it's design to defend against keylogger; I don't know how efficient it is.
The worst is a "PIN" input that is only numbers, and the numbers on the keyboard are behind a modifier key, that you have to hit for every, single, number. Not including negative, separator and decimal characters on number input is worse.
Well, on most "virtual" mobile phone keyboards you can long-press the modifier key in the same way as CAPS LOCK and friends worked on our old mechanical keyboards.
Nevertheless, virtual keyboards need to be improved, and in my opinion it's not the websites faults. It's the browser who has to do its job.
I've used it, it's not a very good experience for conversation... I mostly use gboard, because of gesture input. I'm in several conversations and/or emails a day, I only have to input a numeric pin like described maybe once a month. Doesn't mean it shouldn't be improved on.
Ah true, I forget on my iPad I installed an alternative keyboard. I said Android cause I have more experience using Android. I sort of stopped using my iPad once I bought a Surface Book 2. Since it has a Netflix / Hulu app I dont need my iPad as much anymore.
I have been thinking about a similar question while building a image hosting site.
Which resolution of thumbnail should I provide for each client?
On a desktop, I can be reasonably sure that the user doesn't have limited data or bandwidth, but their resolution (and dpi) might be quite small.
On mobile, the user might have a hiDPI screen which indicates I should send them a high-resolution thumbnail. But I don't know if they would like me spending their limited data or bandwidth that liberally.
So far, I haven't found a way to indicate or request these sort of preferences, but with the up-and-coming support for srcSet, <picture> elements etc., I would love to provide multiple thumbnail alternatives if a client could reasonably decide between them.
As a user, I whish there was an easy way to just change the keyboard to what I want to input. Android/Google keyboard seems to have something like that nowadays (deeply hidden, however), i.e. the possibility to switch to a numeric keyboard, as a user.
Have you tried AnySoftKeyboard on android? It's open source and fully customizable with different layouts and allows you to switch between different entry methods with a swipe or button press.
I've got a QWERTY layout, both regular and one with extra keys for terminals, a full number layout and a keypad layout all easily switchable. It also has what's surprisingly become one of my favourite features, left and right arrows at the top. It helps so much with text navigation, especially when writing long blocks of text.
We were dealing with this today! so we want to use type="number" but it doesn't work!
first, the browser default error message is not accessible.
then we decided to use novalidate="novalidate" to tell browser to not do the validation.
Chrome does not submit the value if the input is not perfect numeric ( try "......"). so it does wipe out user input without letting us catch it on the server!
ZIP code should be a number pad for every American, but if someone ships or bills to Canada then you have to have the letters. Not much you can do about that, unfortunately.
Nope. ZIP codes have to support leading zeros which won't happen with a numeric entry. There could also be a hyphenated +4 suffix for pedants. Post codes must always be treated as text.
