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

The tabs region changes size when the app is moved to monitors with different DPI scaling #1770

New Issue
Closed
opened 2026-01-30 22:36:03 +00:00 by claunia · 6 comments
claunia commented 2026-01-30 22:36:03 +00:00
Owner
Copy Link

Originally created by @rbeesley on GitHub (Jun 19, 2019).

Environment

Windows build number: 18362.175
Windows Terminal version: 0.2.1703.0

Steps to reproduce

  1. Open Terminal on a monitor with 100% scaling.
  2. Drag the Terminal app to a monitor with 150% scaling.

Expected behavior

There should still be room on the title bar to click and move the app.

Actual behavior

The gap between the drop down and the minimize button shrinks to nothing, maybe even with a little overlap. Because of #528, this means that it is likely you won't be able to move the app back after you place it. There is a small gap between the client area and below the system buttons, because the tabs are probably a little too tall for the region, but that is the only space that you can use to drag the app.

Originally created by @rbeesley on GitHub (Jun 19, 2019). # Environment ```none Windows build number: 18362.175 Windows Terminal version: 0.2.1703.0 ``` # Steps to reproduce 1. Open Terminal on a monitor with 100% scaling. 2. Drag the Terminal app to a monitor with 150% scaling. # Expected behavior There should still be room on the title bar to click and move the app. # Actual behavior The gap between the drop down and the minimize button shrinks to nothing, maybe even with a little overlap. Because of #528, this means that it is likely you won't be able to move the app back after you place it. There is a small gap between the client area and below the system buttons, because the tabs are probably a little too tall for the region, but that is the only space that you can use to drag the app.
claunia commented 2026-01-30 22:36:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 19, 2019):

Could we get some screenshots?

I think this will be solved by #929 and it's follow-ups, but I want to make sure.

@zadjii-msft commented on GitHub (Jun 19, 2019): Could we get some screenshots? I think this will be solved by #929 _and it's follow-ups_, but I want to make sure.
claunia commented 2026-01-30 22:36:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 19, 2019):

I'm willing to bet that this was caused by the switch from GetDpiForWindow to GetCurrentDpiScale here... ☹️

@DHowett-MSFT commented on GitHub (Jun 19, 2019): I'm willing to bet that this was caused by the switch from `GetDpiForWindow` to `GetCurrentDpiScale` [here](https://github.com/microsoft/terminal/pull/829/files#diff-e8986dd365aa23a5fbc39a8f26e76d58L94)... ☹️
claunia commented 2026-01-30 22:36:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 19, 2019):

Wait nevermind ignore me

@DHowett-MSFT commented on GitHub (Jun 19, 2019): Wait nevermind ignore me
claunia commented 2026-01-30 22:36:05 +00:00
Author
Owner
Copy Link

@rbeesley commented on GitHub (Jun 20, 2019):

100% Scaling:
image

150% Scaling:
image

@rbeesley commented on GitHub (Jun 20, 2019): 100% Scaling: ![image](https://user-images.githubusercontent.com/3703112/59810044-3dcd1900-92b8-11e9-8ede-65e1c43c453d.png) 150% Scaling: ![image](https://user-images.githubusercontent.com/3703112/59810070-59d0ba80-92b8-11e9-8506-9e79e02d05e5.png)
claunia commented 2026-01-30 22:36:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 20, 2019):

This will definitely be solved by #929.

@DHowett-MSFT commented on GitHub (Jun 20, 2019): This will definitely be solved by #929.
claunia commented 2026-01-30 22:36:05 +00:00
Author
Owner
Copy Link

@aminmesbahi commented on GitHub (Jul 2, 2019):

Same issue when moving between Surfacebook and an FHD monitor
issue

@aminmesbahi commented on GitHub (Jul 2, 2019): Same issue when moving between Surfacebook and an FHD monitor ![issue](https://user-images.githubusercontent.com/866928/60536545-bbaf0c80-9d1b-11e9-9699-ae3105c1f1ff.PNG)
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 Needs-Triage 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#1770
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?