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

Tabs are still padded at the edge of the screen when Terminal is maximized and display scale is not 100% #19658

New Issue
Closed
opened 2026-01-31 06:49:59 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:49:59 +00:00
Owner
Copy Link

Originally created by @JamesBulman on GitHub (Apr 7, 2023).

Windows Terminal version

1.16.10262.0

Windows build number

Microsoft Windows [Version 10.0.22621.1485]

Other Software

No response

Steps to reproduce

Set Windows display scale to 150%
Open Terminal
Maximize Terminal
Open a second tab in Terminal
Click on inactive tab at the top edge of the screen to change between tabs.

Expected Behavior

Inactive tab should activate when Terminal window is maximize and tab is clicked on at the edge of the screen.

Actual Behavior

Inactive tab does not activate.

Originally created by @JamesBulman on GitHub (Apr 7, 2023). ### Windows Terminal version 1.16.10262.0 ### Windows build number Microsoft Windows [Version 10.0.22621.1485] ### Other Software _No response_ ### Steps to reproduce Set Windows display scale to 150% Open Terminal Maximize Terminal Open a second tab in Terminal Click on inactive tab at the top edge of the screen to change between tabs. ### Expected Behavior Inactive tab should activate when Terminal window is maximize and tab is clicked on at the edge of the screen. ### Actual Behavior Inactive tab does not activate.
claunia commented 2026-01-31 06:50:00 +00:00
Author
Owner
Copy Link

@JamesBulman commented on GitHub (Apr 7, 2023):

This is related to issue #2541 and #5881

This feature works correctly when the display scale is set to 100%, but if it is set to a different scale space is introduced between the edge of the screen and the tab. This makes it impossible to click on the tab when the mouse cursor is at the edge of the screen.

This is a video of it working correctly (display scale 100%):

Correct Tab Behaviour

This is a video of it not working (display scale 150%):

Incorrect Tab Behaviour

@JamesBulman commented on GitHub (Apr 7, 2023): This is related to issue [#2541](https://github.com/microsoft/terminal/issues/2541) and [#5881](https://github.com/microsoft/terminal/pull/5881) This feature works correctly when the display scale is set to 100%, but if it is set to a different scale space is introduced between the edge of the screen and the tab. This makes it impossible to click on the tab when the mouse cursor is at the edge of the screen. This is a video of it working correctly (display scale 100%): [Correct Tab Behaviour](https://i.imgur.com/1bCZl5T.mp4) This is a video of it not working (display scale 150%): [Incorrect Tab Behaviour](https://i.imgur.com/1ry63fF.mp4)
claunia commented 2026-01-31 06:50:01 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 11, 2023):

I'm almost certain this is /dup #11309. Seems like it's somehow related to the layout of the monitors itself - I've had no luck in reproing it on my current setup, but I believe that @DHowett has had some luck in the past (if he wants to try and debug it)

@zadjii-msft commented on GitHub (Apr 11, 2023): I'm almost certain this is /dup #11309. Seems like it's somehow related to the layout of the monitors itself - I've had no luck in reproing it on my current setup, but I believe that @DHowett has had some luck in the past (if he wants to try and debug it)
claunia commented 2026-01-31 06:50:01 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Apr 11, 2023):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Apr 11, 2023): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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-2 Product-Terminal Resolution-Duplicate
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#19658
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?