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

Vertical scroll bar too narrow #16669

New Issue
Closed
opened 2026-01-31 05:19:06 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 05:19:06 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (Feb 6, 2022).

The vertical scroll bar was sufficiently narrow so as to make it difficult to use. And, IIRC, someone recently asked about making it wider (I'll second that, a little late). In 1.13.10336.0 it's even narrower than it was previously. Things don't seem to be going in the right direction.

image

Originally created by @vefatica on GitHub (Feb 6, 2022). The vertical scroll bar **was** sufficiently narrow so as to make it difficult to use. And, IIRC, someone recently asked about making it wider (I'll second that, a little late). In 1.13.10336.0 it's even narrower than it was previously. Things don't seem to be going in the right direction. ![image](https://user-images.githubusercontent.com/61856645/152669468-d242f270-b045-4a7a-90a4-5415bba0cb86.png)
claunia added the Needs-TriageResolution-DuplicateTracking-External labels 2026-01-31 05:19:06 +00:00
claunia commented 2026-01-31 05:19:09 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 6, 2022):

This is probably covered by #9218.

@j4james commented on GitHub (Feb 6, 2022): This is probably covered by #9218.
claunia commented 2026-01-31 05:19:09 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Feb 6, 2022):

Other sizes are off too. This pic is from WindowsTerminal 1.12.10334.0. See how the sizes of the images on the icons seem to match.
image
Here's WindowsTerminalPreview 1.13.10336.0. To me the size/boldness difference looks a bit goofy.
image
And I see a separator in 1.13 and not in 1.12.

@vefatica commented on GitHub (Feb 6, 2022): Other sizes are off too. This pic is from WindowsTerminal 1.12.10334.0. See how the sizes of the images on the icons seem to match. ![image](https://user-images.githubusercontent.com/61856645/152692119-301d3904-fac6-4b10-91bd-5925c5fc0020.png) Here's WindowsTerminalPreview 1.13.10336.0. To me the size/boldness difference looks a bit goofy. ![image](https://user-images.githubusercontent.com/61856645/152692200-92aa83e0-e651-4ff5-abd6-6ada8e9fef35.png) And I see a separator in 1.13 and not in 1.12.
claunia commented 2026-01-31 05:19:09 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 6, 2022):

I haven't been following the UI development closely, but I assume at least some of these changes are to match the style guidelines for Windows 11. Those button icons do look more likely to be a bug though.

@j4james commented on GitHub (Feb 6, 2022): I haven't been following the UI development closely, but I assume at least some of these changes are to match the style guidelines for Windows 11. Those button icons do look more likely to be a bug though.
claunia commented 2026-01-31 05:19:10 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Feb 6, 2022):

And colors and fonts have changed (tabs and tab area background). And navigation in the settings UI has changed rather drastically ("General", "Appearance", and "Advanced" no longer have equal status). None of it gets thumbs-up from me.

@vefatica commented on GitHub (Feb 6, 2022): And colors and fonts have changed (tabs and tab area background). And navigation in the settings UI has changed rather drastically ("General", "Appearance", and "Advanced" no longer have equal status). None of it gets thumbs-up from me.
claunia commented 2026-01-31 05:19:10 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 6, 2022):

I'm not a fan of all the new UI changes, but that's always the way of things - you can't please everyone. And maybe one day we'll get the XAML theming functionality (#3327) and I'll finally be able to reskin my terminal in the style of Windows 3.1.

@j4james commented on GitHub (Feb 6, 2022): I'm not a fan of all the new UI changes, but that's always the way of things - you can't please everyone. And maybe one day we'll get the XAML theming functionality (#3327) and I'll finally be able to reskin my terminal in the style of Windows 3.1.
claunia commented 2026-01-31 05:19:11 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Feb 6, 2022):

you can't please everyone

I wonder whom they're trying to please. Maybe someone who likes the changes will chime in.

@vefatica commented on GitHub (Feb 6, 2022): > you can't please everyone I wonder whom they're trying to please. Maybe someone who likes the changes will chime in.
claunia commented 2026-01-31 05:19:11 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 6, 2022):

I agree. I personally do not consider the new scrollbars as optimal for mouse usage. But I can see how they make a lot of sense in the context of most WinUI applications, where overlay scrollbars are beneficial.

However as much as I'd personally like to create an alternative scrollbar appearance, Windows Terminal is still an important test ground for WinUI and while it's not impossible, it's realistically unlikely that we'll adopt something that isn't natively implementable with WinUI. As such foundational UI feedback like this should be directed to https://github.com/microsoft/microsoft-ui-xaml I believe.

@lhecker commented on GitHub (Feb 6, 2022): _I agree._ I personally do not consider the new scrollbars as optimal for mouse usage. But I can see how they make a lot of sense in the context of most WinUI applications, where overlay scrollbars are beneficial. However as much as I'd personally like to create an alternative scrollbar appearance, Windows Terminal is still an important test ground for WinUI and while it's not impossible, it's realistically unlikely that we'll adopt something that isn't natively implementable with WinUI. As such foundational UI feedback like this should be directed to https://github.com/microsoft/microsoft-ui-xaml I believe.
claunia commented 2026-01-31 05:19:11 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Feb 6, 2022):

Windows Terminal is still an important test ground for WinUI

If that's so, I'm confident that those developers are paying close attention to feedback here.

And if feedback should be directed to them that would seem to be the job of the WindowsTerminal team (not mine).

@vefatica commented on GitHub (Feb 6, 2022): > Windows Terminal is still an important test ground for WinUI If that's so, I'm confident that those developers are paying close attention to feedback here. And if feedback should be directed to them that would seem to be the job of the WindowsTerminal team (not mine).
claunia commented 2026-01-31 05:19:12 +00:00
Author
Owner
Copy Link

@mailinglists35 commented on GitHub (Feb 6, 2022):

At this point they can simply remove it, since it's 99% impossible to grab it with the mouse with sufficient reaction time to be useful.

https://i.imgur.com/6Gh2QIa.png

What a mockery, microsoft!

@mailinglists35 commented on GitHub (Feb 6, 2022): At this point they can simply remove it, since it's 99% impossible to grab it with the mouse with sufficient reaction time to be useful. https://i.imgur.com/6Gh2QIa.png What a mockery, microsoft!
claunia commented 2026-01-31 05:19:12 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Feb 7, 2022):

... it's 99% impossible to grab it with the mouse with sufficient reaction time to be useful.

I'll have to agree here. The new 1.13 update brings in a lot of (breaking) changes for Windows 10 users (which according to Microsoft is still supported till 2025). I never had UI problems with Preview updates before, but it is very un-Microsoft-y to neglect old-gen (here, Windows 10) users with usability stuff like this.

I personally do not consider the new scrollbars as optimal for mouse usage.

Please correct me if I'm wrong, but isn't the whole point of having a scroll bar, to facilitate mouse usage? I presume it's going to be problematic even for Windows 11 users (if the width is as narrow there as Windows 10).

@rashil2000 commented on GitHub (Feb 7, 2022): > ... it's 99% impossible to grab it with the mouse with sufficient reaction time to be useful. I'll have to agree here. The new 1.13 update brings in a lot of (breaking) changes for Windows 10 users (which according to Microsoft is still supported till 2025). I never had UI problems with Preview updates before, but it is very un-Microsoft-y to neglect old-gen (here, Windows 10) users with usability stuff like this. > I personally do not consider the new scrollbars as optimal for mouse usage. Please correct me if I'm wrong, but isn't the whole point of having a scroll bar, to facilitate mouse usage? I presume it's going to be problematic even for Windows 11 users (if the width is as narrow there as Windows 10).
claunia commented 2026-01-31 05:19:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 7, 2022):

Alright, thanks for the feedback everyone. I'm gonna move this discussion upstream to https://github.com/microsoft/microsoft-ui-xaml/issues/6684. We'll see if the fix for #9218 is trivial, that might be the easiest, fastest fix here.

@zadjii-msft commented on GitHub (Feb 7, 2022): Alright, thanks for the feedback everyone. I'm gonna move this discussion upstream to https://github.com/microsoft/microsoft-ui-xaml/issues/6684. We'll see if the fix for #9218 is trivial, that might be the easiest, fastest fix here.
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-Triage Resolution-Duplicate Tracking-External
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#16669
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?