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

Navigation menu automatically expands and overlaps settings page content in small windows #22083

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

Originally created by @ghost on GitHub (Aug 10, 2024).

Windows Terminal version

1.21.1772.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

  1. Open Windows Terminal.
  2. Resize the Terminal window to a very small size.
  3. Open the settings page.
  4. Observe that the navigation menu automatically expands and overlaps the content of the settings page.

Expected Behavior

The navigation menu should remain hidden by default in small windows to prevent overlapping with the settings page content.

Actual Behavior

issue

Originally created by @ghost on GitHub (Aug 10, 2024). ### Windows Terminal version 1.21.1772.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce 1. Open Windows Terminal. 2. Resize the Terminal window to a very small size. 3. Open the settings page. 4. Observe that the navigation menu automatically expands and overlaps the content of the settings page. ### Expected Behavior The navigation menu should remain hidden by default in small windows to prevent overlapping with the settings page content. ### Actual Behavior ![issue](https://github.com/user-attachments/assets/371c9122-576d-42d7-83a3-276217fbd806)
claunia added the Issue-BugPriority-3Product-TerminalArea-UserInterface labels 2026-01-31 08:03:02 +00:00
claunia commented 2026-01-31 08:03:03 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 11, 2024):

I think this is duplicate of #16906, and it looks like there is already a PR to fix it - I'm not sure why that hasn't been merged yet.

@j4james commented on GitHub (Aug 11, 2024): I think this is duplicate of #16906, and it looks like there is already a PR to fix it - I'm not sure why that hasn't been merged yet.
claunia commented 2026-01-31 08:03:03 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 11, 2024):

I think this is duplicate of #16906, and it looks like there is already a PR to fix it - I'm not sure why that hasn't been merged yet.

Hi, I don't think this is a duplicate.

I'm mainly wondering why the navigation menu automatically expands and covers the page content, even if the Terminal window is small.

I believe the correct thing to do would be to check the size of the window, and if it is too small, the menu should be hidden by default, but the user can click to open it.

@ghost commented on GitHub (Aug 11, 2024): > I think this is duplicate of #16906, and it looks like there is already a PR to fix it - I'm not sure why that hasn't been merged yet. Hi, I don't think this is a duplicate. I'm mainly wondering why the navigation menu automatically expands and covers the page content, even if the Terminal window is small. I believe the correct thing to do would be to check the size of the window, and if it is too small, the menu should be hidden by default, but the user can click to open it.
claunia commented 2026-01-31 08:03:04 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 11, 2024):

I initially thought it might have been opening the menu intentionally, because in most cases the first thing you'll do is navigate to one of the other sections, and you can't do that in the narrow view without first opening the menu. However, if that was the intention, I would have expected the menu to close as soon you selected something, which it doesn't seem to do. So I think maybe you're right, and the menu should just be hidden by default.

@j4james commented on GitHub (Aug 11, 2024): I initially thought it might have been opening the menu intentionally, because in most cases the first thing you'll do is navigate to one of the other sections, and you can't do that in the narrow view without first opening the menu. However, if that was the intention, I would have expected the menu to close as soon you selected something, which it doesn't seem to do. So I think maybe you're right, and the menu should just be hidden by default.
claunia commented 2026-01-31 08:03:04 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Aug 14, 2024):

Thanks for filing. Looks like the VisualStateManager in the Navigation view is having trouble deciding whether it should be open or closed when you open the settings UI. This should be investigated further in the Navigation view code in XAML directly.

@carlos-zamora commented on GitHub (Aug 14, 2024): Thanks for filing. Looks like the `VisualStateManager` in the Navigation view is having trouble deciding whether it should be open or closed when you open the settings UI. This should be investigated further in the Navigation view code in XAML directly.
claunia commented 2026-01-31 08:03:05 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 15, 2024):

Btw, I forgot to add that I tested this on a Windows 11 machine, and that didn't seem to have this problem (i.e. it doesn't open the settings by default), so this might just be a Windows 10 bug.

@j4james commented on GitHub (Aug 15, 2024): Btw, I forgot to add that I tested this on a Windows 11 machine, and that didn't seem to have this problem (i.e. it doesn't open the settings by default), so this might just be a Windows 10 bug.
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-UserInterface 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#22083
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?