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
☂ Tooltip: open issues to resolve in converged approach #15102
Comments
Re: tooltips dismissing with the ctrl key -- this is indeed what we talked about and settled on as a cross-Microsoft pattern in controls club, so I think it can be considered confirmed :)
"tooltips within tooltips" >>> 😱😱😱 |
something to consider is adding aria-labelledby or aria-describedby to the trigger of the tooltip - this way devs do not have to double the information in the API and would not forget about accessibility. The downside is that if you use one or the other, you need to render tooltip content div always, not only on hover/focus. possible improvement might be to render aria-label if the text is just string. But there is no alternative like this for the description. We currently have this in v0, it would be nice to keep it, at least as optional |
added to list of understood issues
|
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Problems
The v7 Tooltip today is cumbersome to use. Some of the main painpoints:
Expected:
Resulted:
The documented examples say the way to work around this is "use our styling api to set the container to inline-block." The right fix is to not use a wrapper element at all.
Proposals / Ideas
Tooltip
. Let's not have a messy "host" suffix.Tooltip.dismissAll()
static could be nice.Key issue capturing some ideas from awhile back
Active issues the need investigation
Understood issues that need fixing
Tooltip
vsTooltipHost
Need example code of <Tooltip />; Only <TooltipHost /> examples are available #14516Other related issues
The text was updated successfully, but these errors were encountered: