-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Allow custom tree hovers to be markdown #100741
Comments
So I was only able to get my tooltips containing markdown to work by implementing a do-nothing |
Not supposed to happen. I will take a look. |
However, if you tree is going to have many items it is better to set the markdown tooltip in |
@mattacosta I pushed a fix that should be available in insiders tomorrow. |
More feedback: Not sure if anything can even be done about this, but I'm now noticing that it is significantly easier for the cursor to get into the new hovers compared to the native tooltips, thereby preventing them from going away. This makes it more difficult and/or frustrating to select the tree items that it covers. |
I think this is mostly because they are larger, but it would help if the hovers had one of their corners at your mouse, instead of starting where the tree html element starts. @Tyriar would it be possible to do this? |
@alexr00 use |
@Tyriar would it be possible to have the corner of the hover at the mouse instead of in line with the html element it's attached to? |
@alexr00 |
@Tyriar There are things to click and select in the hover, so |
Yep, that's exactly what I mean! That way the behavior is more consistent with the default tooltip and it doesn't obscure all of the tree above it. |
Anything blocking this from moving to Stable? |
Yes, I need to get the hover working properly on resources (files and the like) when they are in the tree. Once that's good, we can move it to stable shortly after. |
|
Currently, the tooltip for custom tree items can only be a string. We should also allow markdown.
The text was updated successfully, but these errors were encountered: