Terminal size changes when dragging window to another monitor #19698

Closed
opened 2026-01-31 06:51:07 +00:00 by claunia · 2 comments
Owner

Originally created by @stevensmedia on GitHub (Apr 12, 2023).

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.0

Other Software

Anonymous Pro font face, 12.0 font size.

Steps to reproduce

Open a new Terminal on my main monitor (3840x2160, 150% scaling)

Its size is 132 columns by 60 rows, which is exactly what my initialCols and initialRows defaults are.

Drag the window over to my second monitor (2560x1440, 100% scaling)

Expected Behavior

The terminal should remain 132x60

Actual Behavior

The terminal is now 127x56

Thank you for your time,

Originally created by @stevensmedia on GitHub (Apr 12, 2023). ### Windows Terminal version 1.16.10262.0 ### Windows build number 10.0.22621.0 ### Other Software Anonymous Pro font face, 12.0 font size. ### Steps to reproduce Open a new Terminal on my main monitor (3840x2160, 150% scaling) Its size is 132 columns by 60 rows, which is exactly what my initialCols and initialRows defaults are. Drag the window over to my second monitor (2560x1440, 100% scaling) ### Expected Behavior The terminal should remain 132x60 ### Actual Behavior The terminal is now 127x56 Thank you for your time,
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:51:08 +00:00
Author
Owner

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

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #6210 for more discussion.

/dup #6210

@zadjii-msft commented on GitHub (Apr 12, 2023): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #6210 for more discussion. /dup #6210
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Apr 12, 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 12, 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19698