For long hovers, errors appear all the way at the bottom and require scrolling

[DanTup]

I'm not sure if this is new, but I'm seeing it a lot lately. When I hover over some code with a red squiggle, if the hover/tooltip has a long description, I have to scroll all the way to the bottom to find the error.

I think it would be better if errors/warnings were either at the top, or somehow docked at the bottom of the tooltip, so you don't have to scroll to get to them. Some tooltips a REALLY long and it's a pain. I'm aware of the F8 functionality, I just prefer the tooltips :-)

[sandy081]

I would prefer the errors/warnings are closer to the cursor i.e at the bottom. It means those views on top of it should not take the complete height.

[DanTup]

I would prefer the errors/warnings are closer to the cursor i.e at the bottom

I think this may depend which way the hover appears? When your cursor is near the top, the box will appear below it, so having them at the bottom is still potentially quite far.

In any case, you shouldn't need to scroll through all of the hover content to see them :(

[rlivings39]

I hit this same issue while implementing a language server. My hover text provider was showing help text for functions that could be large. I saw that the diagnostic wasn't presented and concluded (incorrectly) that hovers and diagnostics were not compatible and disabled hover.

Somehow having the diagnostics be sticky would be my preference. The scrolling would then be per hover section rather than the entire hover panel.

[DanTup]

This was reported by another user:

Dart-Code/Dart-Code#2126

@sandy081 is there a plan to improve this? I understand you want them closer to the cursor, but having to scroll through pages of documentation to figure out what the red squiggle is feels like a really bad UX. Maybe errors could be outside of the scrollable docs (similar to the "Quick fix" section in the screenshots above?)

[vogella]

Pleas fix this, this is really bad UX.

[sandy081]

Sorry have not planned yet.

[fbricon]

Large hover payloads are the norm in Java-land. This is definitely an issue for Java users.
cc @akaroml

[akaroml]

Large hover payloads are the norm in Java-land. This is definitely an issue for Java users.
cc @akaroml

That's why we put the entry "Resolve unknown type" as part of the Javadoc so it shows on top:

@sandy081 We would love to revisit this when the change is in.

[lf-]

This is particularly frustrating in Rust because the Rust compiler often emits diagnostics that cover entire lines, for example, borrow check errors, which overlap a lot of functions, causing the display of both docs and errors on hover, and surfacing this usability issue.

[ppershing]

Would it be maybe possible to let plugins control the ordering? That way, it would be possible to use error "close to the line" for some languages that typically don't have long documentation (e.g. TypeScript, JS, ...) whereas for languages that do have long documentation (Java, Rust, ...) the plugins would be able to show error at the top.

[lnicola]

I don't see why you'd want to have the error at the bottom, since it's presumably the most important thing about that line.

[bsutton]

Can we get action on in this.

It's a constant annoyance they affects every user.

[JRDetwiler]

Is there a priority setting anywhere or is this still an open issue altogether?

[tekert]

I'm amazed this doesn't have the priority it deserves after 3 years, problems are always higher priority on coding. A tooltip should reflect that and also provide ordering of fields.

[mvtec-bergdolll]

@sandy081 this is the current UX:

That's :/

[dunika]

I really don't want to be the guy commenting +1, but in this instance it seem warranted.

It would save me a at least an hour over the course of a year if this was configurable.

[thethongngu]

My current workaround is using Error Lens to show error directly on the editor instead of hovering (and scrolling!). A bit messy but acceptable to me.

[viciousstar]

please fix it.

[ShayBox]

It's even worse: When you scroll down quickly to the bottom, when you reach the bottom it will start scrolling the code editor itself which causes the popup to disappear, so I have to scroll slowly and carefully.

[WynterDing]

It's apparently diagnostic message is more important than other hover message, put diagnostic message on the top should be the basic feature for editor. 😓

[tuliolima]

It would be a great improvement. Always I open the hover with a key shortcut and move the mouse to scroll down it disappears and I need to open again. It bothers a lot.

[azdavis]

I opened this pr which should fix the issue, but it hasn't gotten any attention for the past 3 weeks :/ #166560

[starball5]

Related question on Stack Overflow: How to show error/warning above the documentation in mouse hover popup?

[aiday-mar]

Steps to test:

1. Open a file and type some code with an error, for example a variable which is incorrectly initialized.
2. Hover over this code and verify that the error messages appears first in the hover.