Repository navigation
[Bug]: Tooltips do not disappear in Firefox #6719
Copy link
Copy link
Closed as not planned
Labels
browser-firefoxbugSomething isn't workingSomething isn't workingupstream:vscodeNeeds to be fixed upstream in VSCodeNeeds to be fixed upstream in VSCode
Description
Is there an existing issue for this?
- I have searched the existing issues
OS/Web Information
- Web Browser: Firefox 115 ESR
- Local OS: Debian 12
- Remote OS: Debian 12
- Remote Architecture: amd64
code-server --version:
1.87.0
e5d145fdf32e82be2a0f8de9a3b05f65b13052b6
x64
Steps to Reproduce
- Open code-server in Firefox
- Move your mouse over the file explorer, tab bar or extensions list
- Move your mouse to the text editor
Expected
The tooltips inside the file explorer/tab bar should disappear once the cursor has been moved away from them.
Actual
The tooltips remain until some other pane gets focused, rather than disappearing when the mouse is moved away.
Logs
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. [vscode.ading.dev](https://vscode.ading.dev/?folder=/home/allen/projects/emscripten-libcurl)
INFO Resolving connection token (vscode.ading.dev)... [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
INFO Resolved connection token (vscode.ading.dev) after 2 ms [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
INFO Creating a socket (renderer-Management-ca9e2526-6d59-4bf3-b484-d2c4dc013739)... [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
INFO Creating a socket (renderer-Management-ca9e2526-6d59-4bf3-b484-d2c4dc013739) was successful after 390 ms. [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Loading failed for the <script> with source “https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vsda.js”. [vscode.ading.dev:1:1](https://vscode.ading.dev/?folder=/home/allen/projects/emscripten-libcurl)
The web worker extension host is started in a same-origin iframe! [workbench.web.main.js:1436:12171](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “usb”. [workbench.web.main.js:1436:12576](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “serial”. [workbench.web.main.js:1436:12576](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “hid”. [workbench.web.main.js:1436:12576](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [workbench.web.main.js:1436:12576](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “usb”. [workbench.web.main.js:1436:12723](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “serial”. [workbench.web.main.js:1436:12723](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “hid”. [workbench.web.main.js:1436:12723](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [workbench.web.main.js:1436:12723](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “usb”. [workbench.web.main.js:1436:13483](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “serial”. [workbench.web.main.js:1436:13483](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “hid”. [workbench.web.main.js:1436:13483](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Feature Policy: Skipping unsupported feature name “cross-origin-isolated”. [workbench.web.main.js:1436:13483](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
INFO Creating a socket (renderer-ExtensionHost-d4918a00-2f9a-4f3b-a9e4-9d93e864b029)... [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
INFO [Service Worker] registered [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
INFO Creating a socket (renderer-ExtensionHost-d4918a00-2f9a-4f3b-a9e4-9d93e864b029) was successful after 367 ms. [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. [vscode.ading.dev](https://vscode.ading.dev/?folder=/home/allen/projects/emscripten-libcurl)
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it. [webWorkerExtensionHostIframe.html](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/services/extensions/worker/webWorkerExtensionHostIframe.html?&vscodeWebWorkerExtHostId=471b2a4e-8e3e-4953-b679-56f7a2c4cad3)
Overwriting grammar scope name to file mapping for scope source.js.jsx.
Old grammar file: vscode-remote://vscode.ading.dev/usr/lib/code-server/lib/vscode/extensions/javascript/syntaxes/JavaScriptReact.tmLanguage.json.
New grammar file: vscode-remote://vscode.ading.dev/home/allen/.local/share/code-server/extensions/ms-vscode.vscode-typescript-next-5.3.20230808-universal/syntaxes/JavaScriptReact.tmLanguage.json [workbench.web.main.js:1907:26895](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Overwriting grammar scope name to file mapping for scope source.js.
Old grammar file: vscode-remote://vscode.ading.dev/usr/lib/code-server/lib/vscode/extensions/javascript/syntaxes/JavaScript.tmLanguage.json.
New grammar file: vscode-remote://vscode.ading.dev/home/allen/.local/share/code-server/extensions/ms-vscode.vscode-typescript-next-5.3.20230808-universal/syntaxes/JavaScript.tmLanguage.json [workbench.web.main.js:1907:26895](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Overwriting grammar scope name to file mapping for scope source.ts.
Old grammar file: vscode-remote://vscode.ading.dev/usr/lib/code-server/lib/vscode/extensions/typescript-basics/syntaxes/TypeScript.tmLanguage.json.
New grammar file: vscode-remote://vscode.ading.dev/home/allen/.local/share/code-server/extensions/ms-vscode.vscode-typescript-next-5.3.20230808-universal/syntaxes/TypeScript.tmLanguage.json [workbench.web.main.js:1907:26895](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Overwriting grammar scope name to file mapping for scope source.tsx.
Old grammar file: vscode-remote://vscode.ading.dev/usr/lib/code-server/lib/vscode/extensions/typescript-basics/syntaxes/TypeScriptReact.tmLanguage.json.
New grammar file: vscode-remote://vscode.ading.dev/home/allen/.local/share/code-server/extensions/ms-vscode.vscode-typescript-next-5.3.20230808-universal/syntaxes/TypeScriptReact.tmLanguage.json [workbench.web.main.js:1907:26895](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
INFO Updating additional builtin extensions cache [workbench.web.main.js:651:3372](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. [workbench.web.main.js:1662:12754](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
WebGL warning: drawElementsInstanced: Drawing to a destination rect smaller than the viewport rect. (This warning will only be given once)
[Extension Host] Clang Language Server is now active! [workbench.web.main.js:94:453](https://vscode.ading.dev/stable-e5d145fdf32e82be2a0f8de9a3b05f65b13052b6/static/out/vs/workbench/workbench.web.main.js)
Screenshot/Video
code_server_bug-2024-03-11_12.30.31.mp4
Does this issue happen in VS Code or GitHub Codespaces?
- I tested this in native VS Code.
- This does not happen in native VS Code.
- I tested this in GitHub Codespaces.
- This does not happen in GitHub Codespaces.
Are you accessing code-server over a secure context?
- I am using a secure context.
Notes
This issue does not occur in Chromium-based browsers such as Brave.
This issue did not occur in an older version of code-server which I recently updated from.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
browser-firefoxbugSomething isn't workingSomething isn't workingupstream:vscodeNeeds to be fixed upstream in VSCodeNeeds to be fixed upstream in VSCode
Activity
code-asher commentedon Mar 11, 2024
Could you confirm whether the behavior occurs on Codespaces and/or vscode.dev as well? This very well could be an upstream issue.
code-asher commentedon Mar 11, 2024
Actually nevermind, I just tried and it does not reproduce in Codespaces.
Weirdly, the tooltips there do not seem to obey the theme, so I guess they are native tooltips? But code-server is using non-native tooltips for some reason?
wasalm commentedon Apr 2, 2024
Issue also happens in vscode.dev
Krojack commentedon Jun 5, 2024
Just installed this a few days ago and this is pretty annoying.
code-server: v4.89.1
Code: 1.89.1
Commit: effc6e9
Date: 2024-05-13T18:42:51.662Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0
ben-pearce commentedon Oct 13, 2024
Also experiencing this same issue in Firefox 131.0.2.
A workaround I have found is to set settings.json
workbench.hover.delayto0which stops the tooltips getting 'stuck'. Caveat seems to be that the tooltips don't seem to reliably show in the workbench anymore, although I find this less distracting than the stuck tooltips.simchavos commentedon Mar 6, 2025
Still experiencing this issue in 2025.. Quite annoying, hope this can get looked at!
rowheel commentedon Oct 29, 2025
Same here. Setting these kills the pain, though.
code-asher commentedon Oct 30, 2025
If we can reproduce with
code serve-webwe could report upstream. I think this has got to be an upstream issue, we are not patching tooltips or anything like that. 🤔 But then I am not sure why it seems fine in Codespaces.ading2210 commentedon Jan 28, 2026
I'm still having this issue in 2026, so I looked into it further and found that it also appears on vscode.dev. I have reported the issue upstream at microsoft/vscode#291396
A workaround that doesn't completely disable tooltips (although they don't show up consistently) is setting these options:
{ "workbench.sash.hoverDelay": 0, "workbench.hover.delay": 0 }code-asher commentedon Apr 7, 2026
Very delayed response, but going to close for now and mark it as an upstream issue. Thank you!