Tag Info

Hot answers tagged


Number fields should not always be right-aligned It often makes sense to right-align numbers when they are being compared to other number fields (e.g. in financial statements). This can help comparability and scannability. However, sometimes number fields are unrelated or are mixed with text fields in a form, so left-alignment may promote better visual ...


I see two issues off the top of my head with right aligning text in an input type ="number" When the number selector is not visible it looks quite strange with the number awkwardly floating a bit off from the right. When there is a number already filled in, and you want to add more digits to it, you have to click in the small margin between the last ...


In any population, there will always be some outliers who don't do things the way most of the population does. Someone, surely, will fail to capitalize their name. What's the drawback, if users don't capitalize their own name? Do these names get used in a context where it might reflect poorly on the company? Do the names get used in legal documents or on ...


As with a lot of UX questions, the answer is 'it depends'. Numbers are right aligned because it makes them easier to compare. In an input field however, you may be entering numbers where it makes sense to compare, or you may not. Because you can't say with confidence, it makes more sense to left-align numbers by default than to right align.


Just follow the established search form similar to Amazon one (see below). If the user doesn't select a particular category, then it would search all categories for that particular keyword.


I think search should be a 1-step thing and the categorization should be done by the software/app. If possible, allow the user to search in multiple categories. [Technically speaking, you can use Sphinx for this purpose] One good example of such technique is the older version of Spotlight on Mac. The user types his search query and the system categorizes ...


On Google map (for exemple) you have also one research input field to search many different things (restaurant, street, address, hostel...) So you could use the same behavior : A smart research, but I would add exemples in the input field, like this : You can compile this solution, keeping the category dropdown menu. Here the user has the choice.


I believe that this is well covered by the Forgiving Format pattern. In a nutshell, it says that various dividers and separators might make it easier for a user to read the number and to double-check that the number is indeed correct, but the input field must be smart enough to also accept it without dividers, or with different types of dividers - dots, ...


Whether numbers should be left aligned vs. right aligned (vs. decimal aligned) is based on the context they are being used in. Since that can change, there's no 'correct' default.


Better solution is to use Disk partition kind of UI:- With this kind of UI, users can Allocate people in one control, compared to having one control per activity. Visually get the rough percentage allocation of people for diff activities. Re-sizing the boundary line b/w two activities will change the allocation. Details of the allocation can be ...


Number pickers like the one you have shown are only really useful when there is a small set of numbers to choose from, and ideally you wont have to move to many to get the correct input. The only thing that pops in my mind is to use it for time, such as a timer or alarm. While this particualar example is done with a spinner (iOS Alarm) it could easily and ...


What about something like this? Basically a double range slider where the user sets the boundary between the OK and Warning, and Warning and Critical alerts. The "normal" value is highlighted (popped out) of the usual number range. The user could either drag the little boundary markers or you could make the labels (currently 19, 45, 85, 108) an input field ...

Only top voted, non community-wiki answers of a minimum length are eligible