-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tooltips or static help texts? #21321
Comments
Maybe a clarify documentation under development could resolve the problem? |
Yes, but so far there hasn't been any discussion under this forgotten issue, so I don't know which to choose. |
I guess the answer is: use "tooltip-data-content" as much as possible, because it shows faster than |
Yes, but that is only part of the question.
|
I could agree, if the "each" looks good.
Vue already supports tooltip transparently. See my #23574 |
I vote to use static text as possible. It's clear and with no hidden. Tooltip likes a detailed explanation of a UI element. i.e. when hovering a |
Hmm, as I said: I only partially agree. |
Previously, this setting was pretty confusing for users, especially the difference between "reference" and "issue reference". Related: #21321.
We need clarity on when to use tooltips versus when to use static help texts to describe features.
We certainly need at least one of them for many things that aren't immediately obvious (see i.e. #21306).
PRO tooltips
whenever you navigate on the page
class="tooltip" data-content="Tooltip content"
)CONTRA tooltips
PRO static help text
CONTRA static help text
(do you only need
class="help"
, or do other fomantic UI classes need to be present as well?In parent elements?)
The text was updated successfully, but these errors were encountered: