Forward/Back buttons on mouse do not work in fullscreen/maximized window on macOS Sonoma

[itavero]

Type: Bug

I'm using a Logi MX Vertical mouse, configured via Logi Options+ to use the buttons on the side to go Back/Forward.

1. Open any workspace and browse several files.
2. Maximize the window (in macOS this means that it goes fullscreen and gets its own virtual desktop).
3. Try to go back to the previous file you were browsing using the button configured with the Back action (or forward with the button configured for the Forward action).

Expected behavior: VS Code goes back/forward through the locations I've viewed, just like it does in "windowed" (e.g. non-maximized) mode.

On a (probably) related note: I experience the same in Microsoft Edge. The Back/Forward actions work when it is "windowed", not when the browser is full screen. Other apps do work fine in maximized state though (like Discord for instance).

VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:07:46.768Z) OS version: Darwin arm64 23.5.0 Modes:

System Info

|Item|Value| |---|---| |CPUs|Apple M3 (8 x 2400)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|1, 2, 2| |Memory (System)|24.00GB (0.14GB free)| |Process Argv|--crash-reporter-id 72996b1e-b38b-40ad-b437-9765ab9f6d0f --crash-reporter-id 72996b1e-b38b-40ad-b437-9765ab9f6d0f| |Screen Reader|no| |VM|0%|

Extensions (22)

Extension|Author (truncated)|Version ---|---|--- cpm-cmake-manager|arn|0.0.4 vscode-eslint|dba|3.0.10 gitlens|eam|15.2.3 prettier-vscode|esb|10.4.0 copilot|Git|1.221.0 copilot-chat|Git|0.17.1 vscode-github-actions|git|0.26.3 vscode-pull-request-github|Git|0.92.0 gitlab-workflow|Git|5.4.0 vsc-nvm|hen|0.0.3 cmake-language-support-vscode|jos|0.0.9 cortex-debug|mar|1.12.1 debug-tracker-vscode|mcu|0.0.15 memory-view|mcu|0.0.25 peripheral-viewer|mcu|1.4.6 rtos-views|mcu|0.0.7 vscode-dotnet-runtime|ms-|2.1.1 cmake-tools|ms-|1.18.44 cpptools|ms-|1.21.6 vscode-embedded-tools|ms-|0.7.0 vscode-jest|Ort|6.2.5 cmake|twx|0.0.17

A/B Experiments

``` vsliv368:30146709 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492:30256859 vscod805:30301674 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 2i9eh265:30646982 962ge761:30959799 pythongtdpath:30769146 welcomedialog:30910333 pythonnoceb:30805159 asynctok:30898717 pythonregdiag2:30936856 pythonmypyd1:30879173 h48ei257:31000450 pythontbext0:30879054 accentitlementst:30995554 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 dsvsc021:30996838 724cj586:31013169 pythoncenvpt:31062603 a69g1124:31058053 dvdeprecation:31068756 dwnewjupytercf:31046870 impr_priority:31102340 refactort:31108082 pythonrstrctxt:31112756 wkspc-onlycs-t:31111718 ```

[vs-code-engineering[bot]]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.92.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[itavero]

Just updated to the latest version (v1.92.1 eaa41d57266683296de7d118f574d0c2652e1fc4 2024-08-07T20:16:39.455Z). The behavior is unfortunately still not as expected.

[joshspicer]

Searching online you're definitely not alone with this behavior (in Edge at least): https://www.reddit.com/r/MicrosoftEdge/comments/r27ow0/macos_edge_fullscreen_bug_logitech_wireless_mouse/

[itavero]

@joshspicer While searching I also found that. I figure Edge and VS Code share some common components?

[joshspicer]

VS Code is built using similar technologies as browsers so it's possible there's a connection here.

Do you know if this ever worked as you'd expect?

[itavero]

I can't say for certain. For work I typically use a Windows machine and until recently I used a track pad on my personal MacBook. I switched to the same mouse on my MacBook due to ergonomics.

Given how often I use it and how surprised I was that it didn't work, I'm inclined to say it did work at some point. But then again, I may have not used the full screen mode a lot, as others have been reporting issues like this in Edge since before I started using the mouse with macOS.