Why don’t user agents default to cursor: pointer for buttons?
@simevidas wrote: I’m assuming that cursor: pointer is the optimal value for standard button elements (<button> and the like), from an usability standpoint. However, user agents don’t default to...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@stuartpb wrote: This reminds me, the results of normalize.css should all be added to the HTML Specification as part of the standard (with all divergences officially becoming bugs in the form of spec...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@simevidas wrote: The HTML spec already standardizes certain default styles, doesn’t it? It would be interesting to see a comparison between these standard defaults and the additional rules from...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@MT wrote: cursor: pointer is (similar to text-decoration: underline) typically reserved for links while buttons and links are different things (a link points to a location while a button performs...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@stuartpb wrote: I appreciate the distinction, but today, the notion of "actions" versus separate "locations" is so blurry, I don't feel the distinction is more worth making to the user than the...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@jhnns wrote: I agree with @stuartpb: The distinction is correct, but I don't think that it matters to most users. cursor: pointer is often used for something you can press on. Read full topic
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@stuartpb wrote: Also, if we want to distinguish between types of click that result in different actions, we should be using more types of cursor (as I believe KDE/Konqueror did/does). On that note,...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@simevidas wrote: The spec currently allows fallbacks for image cursors, but only one keyword value can appear, so pointer-link, pointer is not possible. In the absence of anything better, there’s...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@zcorpan wrote: Unknown values make the declaration be dropped, so just do cursor: pointer; cursor: pointer-link; Read full topic
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@simevidas wrote: I’m assuming that cursor: pointer is the optimal value for standard button elements (<button> and the like), from an usability standpoint. However, user agents don’t default to...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@stuartpb wrote: This reminds me, the results of normalize.css should all be added to the HTML Specification as part of the standard (with all divergences officially becoming bugs in the form of spec...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@simevidas wrote: The HTML spec already standardizes certain default styles, doesn’t it? It would be interesting to see a comparison between these standard defaults and the additional rules from...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@MT wrote: cursor: pointer is (similar to text-decoration: underline) typically reserved for links while buttons and links are different things (a link points to a location while a button performs...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@stuartpb wrote: I appreciate the distinction, but today, the notion of "actions" versus separate "locations" is so blurry, I don't feel the distinction is more worth making to the user than the...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@jhnns wrote: I agree with @stuartpb: The distinction is correct, but I don't think that it matters to most users. cursor: pointer is often used for something you can press on. Read full topic
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@stuartpb wrote: Also, if we want to distinguish between types of click that result in different actions, we should be using more types of cursor (as I believe KDE/Konqueror did/does). On that note,...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@simevidas wrote: The spec currently allows fallbacks for image cursors, but only one keyword value can appear, so pointer-link, pointer is not possible. In the absence of anything better, there’s...
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@zcorpan wrote: Unknown values make the declaration be dropped, so just do cursor: pointer; cursor: pointer-link; Read full topic
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@vitim wrote: Besides semantic, what would be a practical difference between pointer, and pointer-link? Read full topic
View ArticleWhy don’t user agents default to cursor: pointer for buttons?
@fvsch wrote: As an answer to the original question, I'll also add that desktop operating systems don't use a "hand" cursor for interactive elements: buttons, menu entries, etc. The hand cursor is...
View Article
