Hot answers tagged input-fields
Simple 2D visual arrangements The visual arrangement of any set of related or similar items will always be subject to some inspection order since deliberate inspection of visuals involve a scan path (subconscious visual processing, particularly of the peripheral view, happens in parallel; but high-level items of interest are scanned using a serial movement ...
Don't over-engineer. Both options you described are very well known and accepted. I don't think that first or second is important in this particular context and both elements are perceived equally already. A new pattern on the other hand would have to be learned and therefore make it harder to use your site.
How about this: Type the first letter of your gender [___]
I had fun making this one but I would never be caught dead actually using it... In order to not show preference obscurity comes in to play: 1. No preference here only information 2. Since there is only one thing to interact with go ahead and click on it One might argue that Both is preferred here but that's okay and should help diversify your data set. ...
This is more a matter of taste & design than usability. Both 1 and 2 indicate that there is some text hidden. Option 3 doesn't always do that, it just depends on the length of the field and the input. So in terms of usability, I'd scratch that one if I were you. Now, comparing red pill vs blue pill. With the red pill you can still see (and select) the ...
Since there is clearly no sensible "default gender", it seems reasonable to me to simply use alphabetical order O Female O Male or ----- Select gender Female Male ------ If your application supports multiple languages, the order could change depending on the language. However, this should neither be particularly difficult to implement, nor will it ...
As long as you are consistent, there isn't anything wrong with putting one on top - say you go alphabetical, then put female first, and don't worry about it. People who search for things to criticize will find ways for it regardless of what you do.
My opinion: If the text is truly useful, don't hide it in a tooltip. If it's not truly useful, don't clutter the screen with a tooltip. For text that is truly useful, ideally it's part of the label itself: Field Title (helpful text here): [ ]
Current Password without a doubt. The typing clarification isn't necessary, and as general rule, if it doesn't make it better, discard it. Consider: That kind of form (password changing) is the same in almost every site. Also it's placed in the same section (edit profile, settings, etc). Inside a text input, specially a password input, to add the "Type ...
I seem to disagree - don't use the third option. If things turn against this design, there is no indication that there might be more text (i.e., when a word nicely ends at the right side - in your case, when the field would have been 5 pixels more narrow). The Red Pill is more innovative (which might or might not fit with your design and target group and ...
Take the red pill! It shows that there is more content without cutting of the data in a hard-edge sort of matter. If the rest of your UI is more of a 'metro' design, use the third option.
You should never limit it, unless you have a very good reason. The users can sometimes innovate in unsuspected ways (it is said that tea bags where for test, and the consumers began to ask it in that way). Comments: A big NO, unless your system has some very strange use. You could wanna talk about a Greek person (say Socrates: Σωκράτης) in Spanish ...
Only top voted, non community-wiki answers of a minimum length are eligible