Use Google+ to Improve Your UI

Post by Groxx » Tue, Jul 19, 2011, 6:49 AM UTC

derefr wrote: post #40

Groxx wrote: post #9

Earlier quoted context omitted.

I, personally, hate buttons without cursor:pointer. Hover effects are nice and all, but they're often rather subtle, and your eyes are attuned to the cursor already. Changing it is extremely visible, and gives you immediate feedback that you're hovering something actionable. Anecdotal, but I find I "see" when my cursor enters a clickable region much more quickly if the cursor changes - I click sooner, rather than mak…

I find that I subconsciously interpret cursor:pointer as "clicking here will do something with GET semantics" vs. cursor:default as "clicking will do something with POST semantics". I feel about the same way about cursor:pointer-styled buttons as I do about plain blue-underlined "Delete" links.

Post by taitems » Tue, Jul 19, 2011, 7:44 AM UTC

Post by mooism2 » Tue, Jul 19, 2011, 8:42 AM UTC

alanh wrote: post #33

ars wrote: post #31

Earlier quoted context omitted.

My rule is add cursor: pointer if you can click on it. Just because browsers didn't do that in the past for form buttons doesn't mean they did the right thing.

Agreed completely. At minimum, and this should be obvious, but you should never leave the text/I-beam cursor on something that can be interacted with (e.g. buttons, sliders, tabs). (I would have only upvoted you, but with hidden scores, who does that help?)