starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request: "Normal" Scrollbar Width / Option to Customize Scrollbar Width in Windows Terminal #23282

New Issue
Closed
opened 2026-01-31 08:37:38 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:37:38 +00:00
Owner
Copy Link

Originally created by @Matzeeee on GitHub (May 22, 2025).

Feature Request: Customizable Scrollbar Width

Problem:
The scrollbar in Windows Terminal is significantly narrower than in most other Windows applications. This can cause usability issues, especially for users with accessibility needs, high-DPI screens, or those using touch input or stylus.

While the scrollbar can be made visible via scrollbarState: "visible", its width and style remain fixed and very slim, making it difficult to interact with.

Suggested Solution:
Please provide an option in settings.json (or via theme support) to adjust the scrollbar width.

Example:

"scrollbarWidth": 12

I generally find it very unattractive when applications create their own interfaces that deviate from the general windows design (configured by user),
especially narrow scrollbars, special title bars, etc.
Narrow scrollbars are difficult to grasp with the mouse and also contradict the freedom from barriers.
If at all, this should only be optionally activated by the user.

Originally created by @Matzeeee on GitHub (May 22, 2025). ### Feature Request: Customizable Scrollbar Width **Problem:** The scrollbar in Windows Terminal is significantly narrower than in most other Windows applications. This can cause usability issues, especially for users with accessibility needs, high-DPI screens, or those using touch input or stylus. While the scrollbar can be made visible via `scrollbarState: "visible"`, its width and style remain fixed and very slim, making it difficult to interact with. **Suggested Solution:** Please provide an option in `settings.json` (or via theme support) to adjust the scrollbar width. Example: ```json "scrollbarWidth": 12 ``` I generally find it very unattractive when applications create their own interfaces that deviate from the general windows design (configured by user), especially narrow scrollbars, special title bars, etc. Narrow scrollbars are difficult to grasp with the mouse and also contradict the freedom from barriers. If at all, this should only be optionally activated by the user.
claunia commented 2026-01-31 08:37:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 28, 2025):

Hey, thanks for the request!

I ... find it very unattractive when applications create their own interfaces that deviate ...

Sorry, I'm afraid I don't understand.

Image

These three scrollbars are from Edge (top, custom scrollbar implementation), Terminal (middle, WinUI 2) and Outlook (bottom, Win32) and represent the three different UI stacks in common use. As far as we can tell, they're roughly the same width/?

I'd rather not add a new setting that lets users introduce further deviation from Windows, for exactly that reason. 🙂

@DHowett commented on GitHub (May 28, 2025): Hey, thanks for the request! > I ... find it very unattractive when applications create their own interfaces that deviate ... Sorry, I'm afraid I don't understand. ![Image](https://github.com/user-attachments/assets/05f8f39c-a2f7-41e0-896e-1418f72e7b7d) These three scrollbars are from Edge (top, custom scrollbar implementation), Terminal (middle, WinUI 2) and Outlook (bottom, Win32) and represent the three different UI stacks in common use. As far as we can tell, they're roughly the same width/? I'd rather not _add_ a new setting that lets users introduce further deviation from Windows, for exactly that reason. 🙂
claunia commented 2026-01-31 08:37:40 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jun 2, 2025):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Jun 2, 2025): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23282
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?