Inconsistent behavior when zooming out #20438

Closed
opened 2026-01-31 07:13:50 +00:00 by claunia · 4 comments
Owner

Originally created by @zamadatix on GitHub (Sep 3, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621.2215

Other Software

No response

Steps to reproduce

Open Terminal, maximize the window, and zoom all the way out (easiest with the mouse wheel). Now run a command which produces a lot of output (e.g. tree) or paste an absolutely enormous amount of text (preferably with no newlines).

Expected Behavior

Terminal uses up screen or has a fixed size maximum that it uses.

Actual Behavior

After these initial steps, Terminal only displays in roughly the top top 1/3 and left 1/2 (i.e. about 1/6th) of the window. Upon resizing, the Terminal now displays in the full scale of the window. Screenshot of the used area of the initial window and then the exact same window after maximising then restoring:

initial

final

Initially I was going to open this as "Terminal lets you zoom too far out" but, actually, it handles it just fine. It's just not consistent about how it handles the size for some reason. Also kudos that this level of zoom somehow works at all!

Originally created by @zamadatix on GitHub (Sep 3, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.22621.2215 ### Other Software _No response_ ### Steps to reproduce Open Terminal, maximize the window, and zoom all the way out (easiest with the mouse wheel). Now run a command which produces a lot of output (e.g. tree) or paste an absolutely enormous amount of text (preferably with no newlines). ### Expected Behavior Terminal uses up screen or has a fixed size maximum that it uses. ### Actual Behavior After these initial steps, Terminal only displays in roughly the top top 1/3 and left 1/2 (i.e. about 1/6th) of the window. Upon resizing, the Terminal now displays in the full scale of the window. Screenshot of the used area of the initial window and then the exact same window after maximising then restoring: ![initial](https://github.com/microsoft/terminal/assets/343550/c0d2005e-6221-40ca-aac9-ad3188d50166) ![final](https://github.com/microsoft/terminal/assets/343550/7fb478b2-ca74-4eda-bc95-40c0e7d1b2d2) Initially I was going to open this as "Terminal lets you zoom too far out" but, actually, it handles it just fine. It's just not consistent about how it handles the size for some reason. Also kudos that this level of zoom somehow works at all!
claunia added the Issue-BugNeeds-Tag-FixProduct-TerminalArea-AtlasEngine labels 2026-01-31 07:13:51 +00:00
Author
Owner

@carlos-zamora commented on GitHub (Sep 6, 2023):

Hi @zamadatix. Can you check if this repros when you're using the atlas engine? It's a checkbox in the Settings UI under the rendering settings.

@carlos-zamora commented on GitHub (Sep 6, 2023): Hi @zamadatix. Can you check if this repros when you're using the atlas engine? It's a checkbox in the Settings UI under the rendering settings.
Author
Owner

@zamadatix commented on GitHub (Sep 7, 2023):

Sorry, I totally forgot to mention this only happens with AtlasEngine enabled!

Edit: Also the close issue button is annoying close to the comment button for my thumbs ;).

@zamadatix commented on GitHub (Sep 7, 2023): Sorry, I totally forgot to mention this only happens with AtlasEngine enabled! Edit: Also the close issue button is annoying close to the comment button for my thumbs ;).
Author
Owner

@zadjii-msft commented on GitHub (Sep 7, 2023):

It only happens with Atlas you say? Well, that's great! That narrows down the bug source considerably. I bet we're just off by one resize or something in atlas.

Thanks for the follow-up!

@zadjii-msft commented on GitHub (Sep 7, 2023): It _only_ happens with Atlas you say? Well, that's great! That narrows down the bug source considerably. I bet we're just off by one resize or something in atlas. Thanks for the follow-up!
Author
Owner

@lhecker commented on GitHub (Sep 7, 2023):

Huh, as it turns out, I think this has accidentally been fixed already: I can't reproduce this on main or on v1.18.1421.0. I'm not sure which commit fixed it, but I'm pretty sure it was #14959.

In other words, if you try Windows Terminal Preview, this issue should not occur anymore. 🙂

@lhecker commented on GitHub (Sep 7, 2023): Huh, as it turns out, I think this has accidentally been fixed already: I can't reproduce this on main or on v1.18.1421.0. I'm not sure which commit fixed it, but I'm pretty sure it was #14959. In other words, if you try Windows Terminal Preview, this issue should not occur anymore. 🙂
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20438