Hi, thanks for reporting an issue with Cursor.
Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.
If you have done so, please check this box.
on
Describe the Bug
The setting workbench.editor.mouseBackForwardToNavigate
should allow using the global Back/Forward buttons to navigate in Cursor. This works properly in vanilla VS Code. In addition, a difference in VS Code ↔ Cursor is that in Keybindings assignment, VS Code will detect “ctrl±” when pressing the mouse back button, but Cursor will not detect any input.
Steps to Reproduce
- Example hardware: Logitech MX Master 3 mouse
- Enable workbench.editor.mouseBackForwardToNavigate setting
- Press the mouse back/forward buttons
Expected Behavior
The mouse back/forwards buttons should trigger the workbench.action.navigateBack
and workbench.action.navigateForward
commands.
The keybinding editor should detect back/forward mouse buttons as ctrl+-
and ctrl+shift+-
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.2.0
Additional Information
This has been my only major pain point converting from VS Code → Cursor. It’s a critical part of my workflow, so while Cursor isn’t unusable, this negatively impacts my flow with Cursor several times per day.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor