-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Terminal hover positioning is unfriendly #162336
Comments
Do we know if there's a good reason we haven't respected the mouse position in the editor case? Seems like it would be a good idea to update both if there isn't one. |
@daviddossett these are general editor hovers rules I think, for example it works well here as you read the symbol and info is directly above: Not sure about the decision that went into that, but it's probably something around keyboard interaction being the typical way to trigger the hovers, which doesn't apply as much to links. |
The reason was, as @Tyriar mentioned, to align the hover with the current word / symbol being hovered. Over the years, we've added a range property to a hover result, where a hover provider can express what range their hover applies to, and we moved to use that. Most of the times, that range is something sensible, like the current word/symbol. But I agree that this doesn't work very well if the range is a lot larger, if it begins far away from the mouse position or on a wrapped line, etc. This came up a lot over the years, I'll look into improving things. |
The editor positioning is now improved via #163970 , let's keep this issue around to track the terminal hover positioning. |
Was able to repro this today on stable 1.95.3(f1a4fb) so the issue still exists. |
echo https://github.com/microsoft/vscode/pull/162335
Screen.Recording.2022-09-29.at.14.21.44.mov
The text was updated successfully, but these errors were encountered: