4 ms·

the problem is mobile keyboards. pulling up a numeric keyboard to enter a cc number is helpful, but also lacks a space key, making it hard to viaually verify a

the problem is mobile keyboards. pulling up a numeric keyboard to enter a cc number is helpful, but also lacks a space key, making it hard to viaually verify a 4-4-4-4 pattern. yes, there's luhn, but that doesnt work until you're finished (same problem with formatting post-entry, eg onblur/onchange) for entering a date, most numeric keypads lack /. thankfully, phone entry is mostly covered with type=tel. which is numeric + symbols, so i end up using it as a hack for some other numeric types, as suggested on SO. i would rather just type big numbers instead of fumble with symbols or tiny keys on a full keyboard for numeric inputs.

TeMPOraL 8y ago
> the problem is mobile keyboards. So much work is put into making various pointless design gimmicks recognize whether they're displayed on mobile vs. desktop. Why not recognize whether the user is on mobile (and thus likely has crappy keyboard), and conditionally enable those convenience factors? Also, I feel this problem was solved 20+ years ago with CD-key entry boxes. You'd have a row of text boxes, 2-4 characters long each, but they behaved as if they were one large text field - the focus correctly jumped between the boxes as you wrote or erased stuff.
- franga2000 8y ago
  > CD-key entry boxes Unless you missed one character and then everything was misaligned and it wouldn't let you just insert one in the middle so you had to delete everything after that point and start over. Meanwhile, your pirate friends were already at level 10.
  - TeMPOraL 8y ago
    Nah, the ones I'm thinking of were made of native Windows text field controls, so arrow keys & all worked within them (and AFAIR transparently moved between them), and Tab/Shift+Tab behaved correctly too.
johnnycake12 8y ago
> the problem is mobile keyboards. No, that's just the default iOS keyboard, meaning the problem is Apple. My Pixel's keyboard sensibly has a space button, as do most 3rd party keyboards on iOS.
- leeoniya 8y ago
  there are actually several variants of keyboards on all devices (not just numeric or alphanumeric). the phone entry keyboard is different, and there are a couple others. it's not just iOS. to make the right one pop up in ios you have to do stuff like pattern=[0-9]*, but that becomes restrictive, too. http://blog.pamelafox.org/2012/05/triggering-numeric-keyboards-with-html5.html http://blog.pamelafox.org/2012/05/triggering-numeric-keyboar...

TeMPOraL 8y ago

> the problem is mobile keyboards. So much work is put into making various pointless design gimmicks recognize whether they're displayed on mobile vs. desktop. Why not recognize whether the user is on mobile (and thus likely has crappy keyboard), and conditionally enable those convenience factors? Also, I feel this problem was solved 20+ years ago with CD-key entry boxes. You'd have a row of text boxes, 2-4 characters long each, but they behaved as if they were one large text field - the focus correctly jumped between the boxes as you wrote or erased stuff.

franga2000 8y ago
> CD-key entry boxes Unless you missed one character and then everything was misaligned and it wouldn't let you just insert one in the middle so you had to delete everything after that point and start over. Meanwhile, your pirate friends were already at level 10.
- TeMPOraL 8y ago
  Nah, the ones I'm thinking of were made of native Windows text field controls, so arrow keys & all worked within them (and AFAIR transparently moved between them), and Tab/Shift+Tab behaved correctly too.

johnnycake12 8y ago

> the problem is mobile keyboards. No, that's just the default iOS keyboard, meaning the problem is Apple. My Pixel's keyboard sensibly has a space button, as do most 3rd party keyboards on iOS.

leeoniya 8y ago
there are actually several variants of keyboards on all devices (not just numeric or alphanumeric). the phone entry keyboard is different, and there are a couple others. it's not just iOS. to make the right one pop up in ios you have to do stuff like pattern=[0-9]*, but that becomes restrictive, too. http://blog.pamelafox.org/2012/05/triggering-numeric-keyboards-with-html5.html http://blog.pamelafox.org/2012/05/triggering-numeric-keyboar...