Skip to content

Inconsistent behavior when zooming out #15925

Closed

Description

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!

Activity

  1. added
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Sep 3, 2023
  2. carlos-zamora commented on Sep 6, 2023

    @carlos-zamora

    Hi Daniel Smith (@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.

  3. zamadatix commented on Sep 6, 2023

    @zamadatix
    Author

    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 ;).

  4. added
    Needs-AttentionThe core contributors need to come back around and look at this ASAP.
    and removed
    Needs-Author-FeedbackThe original author of the issue/PR needs to come back and respond to something
    on Sep 6, 2023
  5. added and removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    Needs-AttentionThe core contributors need to come back around and look at this ASAP.
    on Sep 7, 2023
  6. zadjii-msft commented on Sep 7, 2023

    @zadjii-msft
    Member

    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!

  7. lhecker commented on Sep 7, 2023

    @lhecker
    Member

    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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-AtlasEngineIssue-BugIt either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions