Use pointer cursor, not help cursor, with tooltips

[basham]

From the following Skype conversation, we determined that tooltips should use the pointer cursor, not the help cursor.

[11/4/13, 2:35:54 PM] Kristol Hancock: Hey everyone! Quick q for u. I am working on defining the interaction for the context-sensitive help for KSAP. Here is the current design: http://ux.ks.kuali.org/wireframes/KSAP/Sprint_014/KSAP-137_ContextHelp/index.html. Only the FA13 links work. David P asked if I wanted to change the cursor to a question mark when mousing over the term, as shown here: http://www.w3schools.com/cssref/playit.asp?filename=playcss_cursor&preval=help. That seemed like more of a core UX question, so I thought I'd post it here. Thoughts?

[11/4/13, 2:45:18 PM] Erik Rath: My initial thought is that it may be a bit too much. As we are already using the convention of the dotted underline, having the cursor change won't add a lot of value and will create more visual noise as the user works on the page.

[11/4/13, 2:52:55 PM] Kristol Hancock: sounds reasonable to me. thanks, Erik!

[11/4/13, 3:32:13 PM] Chris Basham: Talked it over with Tara. We agree with Erik. The help cursor is a bit much, especially in an interface in which it's used so extensively. Given the tooltip appears upon clicking/tapping, the cursor should remain as a pointer cursor, so the interface better communicates what the user should expect. If, instead, the tooltip appears upon hover, a help cursor may be more acceptable. (We should reevaluate the hover case, if it would come up.)

Kristol, I don't know if it was a consequence of Axure or intentional, but it's important for the text to have dotted, rather than dashed, underlines as Erik said, since that's the widespread convention. If you've seen otherwise or if you have an argument for dashes, please elaborate so we can discuss further.