On Monday, January 19, 2004, at 12:20 PM, Taco Fleur wrote:
What do you reckon, a Rave or Valid point?
http://www.tacofleur.com/index/blog/archive/2004/01/?141800
My answer (also posted as a blog comment):
Form widgets come from the user's OS (Operating System) or UA (User Agent/Browser), and (IMHO) should behave in a manner to which the user is accustomed. Adding a cursor hand to the button may seem like you're helping the user by adding a visual cue, but you may in fact be confusing the user, and degrading the user experience.
It's for this very same reason that I try not to style form elements much beyond their default stylings as supplied by the OS/UA.
It's also for this very same reason that I dislike what Mozilla does with form widgets, which (at least on Mac OS 9 & OS X) differ dramatically from the rest of the OS.
The only time I'd use "cursor: hand;" is if the object's action was implemented with a JS onlick='' event, rather than a <a href=''>...</a> tag. But I can't see this happening too often, given that non-JS users would be disadvantaged.
Extensive user testing would reveal the true answers though.
Justin French
*****************************************************
The discussion list for http://webstandardsgroup.org/
*****************************************************
