microsoft
[ux] `window.titleBarStyle: "custom"` causes rightmost pixels to resize window instead of actioning scrollbar
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.85.2, 1.86, 1.88.1
- OS Version: reproducible on:
- Windows 10 up-to-date
- Debian 12 up-to-date, GNOME Shell 43.9, Xorg
- Arch Linux up-to-date, GNOME Shell 45.3 & 46.0, Wayland 1.22.0
Steps to Reproduce
- Set pref
window.titleBarStyleto"custom" - Tile VSCode to the right of the screen (under Windows or GNOME Shell: Meta+Right)
- Try to scroll by clicking the right scrollbar at the right edge of the screen (the right-most column of pixels of the screen)
Expected: the scrollbar gets clicked and the buffer viewport scrolls up/down.
Actual: a window border gets clicked and the window resizes. This is annoying because it breaks "throw mouse to very right and click", said differently it breaks Fitt's Law, by increasing distance/difficulty to hit the right scrollbar.
Screencast
https://github.com/microsoft/vscode/assets/522085/8a634c57-ec98-42f1-94a9-6c1863623279
Hi @sbatten. Our bot friend VSCodeTriageBot assigned this to you for triage several months ago. Any chance you look into it, or re-assign to someone for triage?
This bug remains reproducible today, and I updated the description to reflect today's versions of everything.
(This will be my only follow-up. I understand you might be busy and I don't wish to harrass. I'm doing this one-time ping because this VSCodeTriageBot assignment means you do have a process, so here’s a single follow-up in case this issue slipped through the cracks).
Thank you.
VS Code 1.98 release notes: “We are happy for continued feedback on [Custom title bar on Linux] and are already working on improving this for future milestones based on existing feedback.”
@rzhao271 @sbatten given this explicit call to feedback, here’s me pinging you that I would like to use the custom title bar, but cannot, because of this accessibility regression it causes. It’s still happening as of 1.98. Hope you can fix it.
This reproduces with a minimal Electron app too: https://github.com/electron/electron/issues/45916
