blog! “I can't use my number pad for 2FA codes”
This has to be the most infuriating bug report I've ever submitted. I went to type in my 2FA code on a website - but no numbers appeared on screen. Obviously, I was an idiot and had forgotten to press the NumLock button. D'oh! I toggled it on and typed again. No numbers appeared. I […]
⸻
#HTML #javascript #security #ui #ux
@Edent typo: "Develops often use"
@Edent Sorry, our app only supports 60% layout mechanical keyboards, it's in the TOS.
@lewis Dvorak or GTFO!
Can't boost this enough.
I've experienced this in the past, too.
It matches the lack of thinking of the devs that block copy/paste.
@Edent You are correct, JavaScript was a mistake.
@Edent the bright javascript developers who decided to override system input mechanisms are fucking anathema.
(in many payment interfaces i cannot use compose key to type my proper name because some fucking genius decided that they will accept only raw keystrokes. ah, and of course no paste. because why would i want to paste my credit card number from my secret vault, when i can fucking type it.)
@Edent Now I wonder if it would be possible to change that JavaScript to accept keys instead of codes, using tampermonkey or something similar...
That’s almost as bad as when they disable pasting into password fields. Way to encourage people to use crappy short passwords.
IMO browsers shouldn’t even permit that. It’s -my- browser on -my- computer. If I want to paste and the websty doesn’t want me to, too bad. I could not care less about what they want even if you paid me to.