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.