3 ms·
The worst number input that I've seen is some Windows input, in which the value must always be valid and in the allowed range. So, say, the current value is ‘30
by aasasd 4y ago
The worst number input that I've seen is some Windows input, in which the value must always be valid and in the allowed range. So, say, the current value is ‘300’ and you want ‘100’—but you can't backspace over the ‘3’ and enter ‘1’. If the value is ‘350’ and you want ’100’, you can't even select ’35’ and type ‘10’, because the input will freak out midway and immediately replace the value with the allowed minimum. Moreover, how do you even type the number you want if the input can't be empty? If the minimum is 20, you can't ever type anything from scratch without doing some select-replace gymnastics, because every digit will be immediately replaced with the value 20.
Can't remember which app it was, and if it was a standard input from one of the dozen MS frameworks—but the testers on it must've been mightily incompetent. Imagining for a second that someone worked on that is like catching a glimpse into an abyss of pure stupidity. After this horror I'm quite relaxed about problems with inputs that at least allow me to type the damn number.
- nijave 4y agoReminds me of the inputs that try to be clever with formatting and move the cursor around and insert characters (happens with dates a lot). When you try to backspace, the input cleverly re-inserts the divider and moves you forward again
- temp_account_32 4y agoYeah this does sound very user unfriendly, although I have to say a good validation UX is particularly difficult to code (When to validate, on submission or on losing focus to that element or instantly on input? Do you need to debounce the validation? How to present validation error messages and where? Etc.). Your example probably stemmed from the case that the developer wanted the user to have instant feedback on validation, and instead of displaying some validation error message next to the input, they decided f-it - let's just immediately validate on input and not allow any invalid input. Bad/lazy decision, but I can see how it came to be.
- montag 4y agoI accidentally implemented this behavior in a number input recently. Felt stupid after fixing it. This stuff can happen so easily when people don't use the stuff they build.
- quickthrower2 4y agoTesters may have found it, raised bug, got rejected as non-issue “as spec” whatever. Who knows.
- aasasd 4y agoWell, I haven't been a tester, much less in a desktop app or a game company, but I'm vaguely confident that a tester's job is to raise hell, and this sure deserves it. As a ‘senior dev’ I've killed some sponsored, money-backed changes because they would require revising how the site's backend works on a basic level. IMO what this tester should've done is to show the behavior to any dev with a semblance of clout.