5 ms·
That's only half of the argument. The other half being that, after having text in there (say, in the edit form of a CRUD app), your user no longer remembers wha
by Pewpewarrows 14y ago
That's only half of the argument. The other half being that, after having text in there (say, in the edit form of a CRUD app), your user no longer remembers what that field was supposed to represent to begin with.
- jaggederest 14y agoProbably browser-specific, but some browsers will show the placeholder or label with a hover, as well.
- gedrap 14y agoBut hovering to see the label is not intuitive at all
- Dylan16807 14y agoIt's not? The world of computers is filled with hovering for descriptions and details.
- gedrap 14y agoIt is but an input field is not really an element you would hover for more info. If additional info for the user is required, some question mark icon next to field does the job well because it yells 'hey! something might be confusing or not so obvious'. I might be an exception but can't recall a case when I would hover input field.
- julian37 14y agoYeah but that doesn't make it a good idea.
- anotherbadlogin 14y agoDelay-based UI is shitty UI. Do you have so little regard for your users that you think their time is free? Not to mention that hovering over text fields is not the norm, because they are fields and fields have labels. Hovering over buttons with cryptic icons? Maybe.
- fokov 14y agoRequiring users to hover to determine the context is a horrible UX. Tooltips/popup descriptions should only be used to provide additional information that isn't required.
- Raphael 14y agoYou can set the title attribute to the same as the placeholder.
- lancefisher 14y agoYou can't really hover with your finger on an iPhone.