Tag Info

New answers tagged

1

Generally speaking, especially for text type input or textarea field, it is better to keep the existing text upon validation error. However, depending on your actual scenario, there may be other decision making steps that you might need to consider: If it is in a totally wrong format. Example you requested for numbers and the user fills up the field with ...


4

Why not provide a way for user to do both ? Data can be left intact as suggested by others and providing a small "X" button/icon ( similar to the magnifying glass icon usually seen in search boxes) at the end of text box to clear the whole thing if the user intends to.


24

From a usability point of view, definately keep their entry there. There is nothing more annoying to users, in our experience, than clearing their entry on failing validation. They need to be able to see what they have done wrong, and if you clear it they are having to use their memory.


80

Typing on mobile is a very arduous and unpleasant process, so we should try keeping it to a minimum. Sometimes your users will have made just a small error that can be fixed by replacing or adding a character or two (typically they typed something instead of @ in an email address etc.). Sometimes they will have made a big error and they need to retype the ...


1

The reason is typically because they either don't work with a UX team, or ignore the UX team. Bad validation typically comes from inheriting bad validation and bad validation habits. They've been cutting-and-pasting default field validations for the past decade and just keep on doing the same with little thought put towards determining if the validation ...


3

I've been apart of numerous projects, as a UX professional, where the project is led by the tech team, and one big fault in all of this, is that the tech leads believe they know everything about UX practices and start saying, "I do it this way, therefore..." That's where it all begins... I also had a meeting where a tech lead says,"we should do it this way ...


2

Because an extremely large proportion of programmers out there have no idea that there IS a standard, let alone what that standard might contain. When they need to validate, they just make something up based on their (absurdly) limited experience and call it a day. Since such characters are relatively rare in e-mail addresses, they don't get called on their ...


0

You should try to reject possible invalid entries before they get stored to your backend. For the simple reason that no additional controls are required and you can do this completely without any additional user interaction. And as you're saying that it would solve 99% this way and it's a monkeypatch after all, this has to be your first step. If the ...


0

Send your customers/citizens instructions by mail or e-mail. In your error message make a reference to these instructions, without giving any details.


3

Lets think of the scenario, where a legitimate user and a malicious user typing in an SSN/IBAN/VAT number: Legit User: There is a good chance that the user has memorized the number or written it on a piece of paper/text file. In this case, notifying a user that "The number you entered seems to be incorrect. Please check again." is perfectly enough. User ...


1

For security reasons you don't want to give away the full formula of how the field is validated. However just showing 'invalid input' isn't really a useful phrase here. You wouldn't say that phrase in real life if someone said something wrong to you. It depends how intelligent you want the message to be really. If someone enters a value that is too long ...


0

It's actually pretty common these days for forms to show correct/incorrect data entry as you go. Usually I see it in the form of either a green check mark or red X showing up on next to each entry. Usually it either happens while you're filling the field out, or as soon as you move on to the next field. It definitely makes it easier to fill out a form if ...


0

What is a valid user name? Is it a user name that was sent to the user from the application when he or she signed up? if so, you should indicate it instead of a generic "Please enter a valid username." If the user name is what the user entered when signing up, you should have a link "forgot my user name." Users are forgetful, and instead of making them ...



Top 50 recent answers are included