Skip to content

Ctrl+hover over file paths shows empty tooltip #4187

Closed

Description

@DanTup

Split from #4181, raised by @gspencergoog. This happens when you hover over a path and hold Ctrl (I had to also then move the mouse around, though I don't know why):

image

I believe this may be because we're returning 0-width target ranges and VS Code wants to show a preview. We may need to verify whether that's a bug (and VS Code should handle it), or if they expect us to return the whole file as a range when the link is to a file. I noticed the VS Code APIs appear to support Positions in some places where the LSP spec seems to only support Range.

Activity

  1. added this to the On Deck milestone on Sep 28, 2022
  2. DanTup commented on Sep 28, 2022

    @DanTup
    MemberAuthor

    I think this might be best fixed in VS Code (I think empty ranges are reasonable for files - TypeScript has them too). I've filed microsoft/vscode#162227. Although it could be argued we should select "the entire file", it's very possible the file is actually empty.

  3. DanTup commented on Dec 7, 2022

    @DanTup
    MemberAuthor

    This was fixed in VS Code via microsoft/vscode#162227.

  4. added and removed
    in editorRelates to code editing or language features
    on Dec 7, 2022
  5. removed this from the On Deck milestone on Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions