microsoft / microsoft/terminal

Sometimes maximized conhost/cmd windows have the bottom line(s) off the bottom of the screen

Open
#10,410 2 comments 1 reaction 0 assignees View on GitHub
Area-Interaction Help Wanted Issue-Bug Priority-3 Product-Conhost
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

### Windows Terminal version (or Windows build number)

10.0.22117.0

### Other Software

_No response_

### Steps to reproduce

I am TS'ed to my dev machine at work. I maximize a [traditional conhost] cmd window (running razzle, then pwsh+PSReadLine on top of that). I disconnect, then reconnect later, and the cmd window is still maximized as expected. But *sometimes* the active prompt is below the visible portion of the window, usually by several lines--I can't see what I am typing while I type it; but when I hit [enter] and the buffer scrolls up, then I can see what I just typed. If I restore the window then re-maximize it, the problem is gone. The rest of the window UI looks fine (like the scrollbar on the right); the problem is not the outer window becoming the wrong size.

What should I gather to help troubleshoot this? It only happens *sometimes*, and I can't repro on-demand. Is there some low-impact tracing I can leave on, or should I just gather dumps of the associated processes?

### Expected Behavior

I expect that when I reconnect to my TS session, and type into my maximized cmd window, I can see the text I am typing, as I type it.

### Actual Behavior

The text I am typing is happening below the bottom of the cmd window--if I press enter a few times, it gets scrolled up into the part of the buffer I can see.

Contributor guide

Open the contributing guide

Research direction

Start by examining the reported sequence: maximize a traditional conhost cmd window, run razzle and pwsh+PSReadLine, disconnect from the Remote Desktop session, then reconnect. Compare the maximized view with restoring and re-maximizing, and gather the low-impact tracing or associated-process dumps requested in the report; done means identifying evidence for why the prompt is below the visible window.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, powershell
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.