Package-created popup remains stuck on screen

[oprearocks]

Description

When using github.com/microsoft/TypeScript-Sublime-Plugin I get its short documentation popups stuck on the screen without any way to remove them other than closing and reopening Sublime Text.

Steps to reproduce

1. Install https://github.com/microsoft/TypeScript-Sublime-Plugin
2. Open a new file and start writing TypeScript code
3. Randomly, one or more popups will appear on the screen and will not disappear

Expected behavior

Popups disappear either when I continue typing or when I dismiss them using the "Esc" key or a dedicated keyboard shortcut for hiding and showing that part of the popup.

Actual behavior

Popups randomly remain pinned to the screen and cannot be removed, preventing normal code editing.

Environment

• Build: 4101
• Operating system and version: macOS Big Sur version 11.2.3

Links

Linked issue filled on the plugin's GitHub Issues page: microsoft/TypeScript-Sublime-Plugin#760

[wbond]

As someone who doesn’t write TypeScript, can you suggest a project to clone and an example file with input that triggers this?

[jgburet]

This indeed sometimes happen when you hover something and move away your cursor to a different view (so it only happens here when I have more than one view).

This rarely happen compared to the annoying behavior where a documentation pop-up is instantly (really snappy, like a quater of a second) replaced by another pop-up listing all the links to references...

[rchl]

To reproduce try:

1. Clone https://github.com/rchl/lsp-log-parser
2. In cloned directory run yarn to install dependencies (or npm i if you don't have yarn).
3. Open models/parsers/log-parser.ts file
4. At the end of the file type something like [].forEach(function() {})

The issue should trigger after typing the ( after function.

Screen_Recording_2021-04-08_at_20.19.34.mov

@jgburet The issue with popup not disappearing is in ST, I believe, but the other issues you are seeing are due to how the Typescript package is implemented. I recommend using LSP-typescript (+LSP) package instead. It doesn't have all those issues and makes use of ST4 features to make the experience even better.

[BenjaminSchaaf]

Fixed in build 4102.