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

NavigationView's scrollbar covers up icons when accessibility feature is enabled #12203

New Issue
Open
opened 2026-01-31 03:08:57 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:08:57 +00:00
Owner
Copy Link

Originally created by @jtippet on GitHub (Jan 26, 2021).

  1. Go to Settings app > Ease of Access > Display
  2. Clear the box next to "Automatically hide scroll bars in Windows"
  3. Launch Terminal
  4. Size the Terminal app so its left-hand NavigationView is in compact mode, but not completely hidden
  5. The scrollbars encroach on the icons on the left side:
    image

Apparently this is MUX bug 2376, wherein they wash their hands and point at you -- it's somehow the app's fault that this happens.

Note that the other intrusive scrollbar is MUX bug 3771, which they haven't punted yet.

Originally created by @jtippet on GitHub (Jan 26, 2021). 1. Go to Settings app > Ease of Access > Display 2. Clear the box next to "Automatically hide scroll bars in Windows" 3. Launch Terminal 4. Size the Terminal app so its left-hand NavigationView is in compact mode, but not completely hidden 5. The scrollbars encroach on the icons on the left side: ![image](https://user-images.githubusercontent.com/10259764/105825949-097e0c00-5f75-11eb-8dd2-9466d0745df4.png) Apparently this is MUX bug 2376, wherein they wash their hands and point at you -- it's somehow the app's fault that this happens. Note that the *other* intrusive scrollbar is MUX bug 3771, which they haven't punted yet.
claunia added the Help WantedIssue-BugPriority-3Product-TerminalArea-SettingsUI labels 2026-01-31 03:08:57 +00:00
claunia commented 2026-01-31 03:08:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 26, 2021):

That's super annoying. I get their reasoning (https://github.com/microsoft/microsoft-ui-xaml/issues/1742#issuecomment-563390861), but still, kinda seems annoying that there's this obvious scenario where most/all apps will break.

To my understanding this is "fixed" in the sense that an app developer can now use the CompactPaneLength API of the NavigationView to set an increased compact pane width if required.

The WinUI team opted for this per-app approach instead of a global change as reasoned here.

I wonder if there's a way to only make it bigger when we detect that setting is enabled?

@zadjii-msft commented on GitHub (Jan 26, 2021): That's super annoying. I get their reasoning (https://github.com/microsoft/microsoft-ui-xaml/issues/1742#issuecomment-563390861), but still, kinda seems annoying that there's this obvious scenario where most/all apps will break. > To my understanding this is "fixed" in the sense that an app developer can now use the [CompactPaneLength](https://docs.microsoft.com/en-us/uwp/api/microsoft.ui.xaml.controls.navigationview.compactpanelength?view=winui-2.3) API of the NavigationView to set an increased compact pane width if required. > > The WinUI team opted for this per-app approach instead of a global change as reasoned [here](https://github.com/microsoft/microsoft-ui-xaml/issues/1742#issuecomment-563390861). I wonder if there's a way to only make it bigger when we detect that setting is enabled?
claunia commented 2026-01-31 03:08:58 +00:00
Author
Owner
Copy Link

@jtippet commented on GitHub (Jan 26, 2021):

Last time I grappled with a scrollbar bug, I couldn't find any clean way to detect the width of a scrollbar from app code. I might have overlooked something, or there might have been a new development since. But the documentation still says "oh just leave a 16px gutter anywhere a scrollbar could appear, just in case! 🤞"

So my takeaway was that the OS should not have given users a checkbox that lets them fiddle with the width of apps' scrollbars until the OS exposes better APIs for apps to cope with such a gotcha.

@jtippet commented on GitHub (Jan 26, 2021): Last time I grappled with a scrollbar bug, I couldn't find any clean way to detect the width of a scrollbar from app code. I might have overlooked something, or there might have been a new development since. But [the documentation](https://docs.microsoft.com/en-us/windows/uwp/design/controls-and-patterns/scroll-controls) still says "oh just leave a 16px gutter anywhere a scrollbar could appear, just in case! 🤞" So my takeaway was that the OS should not have given users a checkbox that lets them fiddle with the width of apps' scrollbars until the OS exposes better APIs for apps to cope with such a gotcha.
claunia commented 2026-01-31 03:08:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 26, 2021):

Yea, it's not great. This is how we've been doing it so far, and that seems to work

b50df20cfe/src/cascadia/TerminalControl/TermControl.cpp (L2723-L2725)

but that might also be us relying on coincidence.

@zadjii-msft commented on GitHub (Jan 26, 2021): Yea, it's not great. This is how we've been doing it so far, and that seems to work https://github.com/microsoft/terminal/blob/b50df20cfe94a78b235c233401e4df037f818e7b/src/cascadia/TerminalControl/TermControl.cpp#L2723-L2725 but that might also be us relying on coincidence.
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 Area-SettingsUI Help Wanted Issue-Bug Priority-3 Product-Terminal
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#12203
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?