starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Open
opened 2026-01-31 04:03:52 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:03:52 +00:00
Owner
Copy Link

Originally created by @jazzdelightsme on GitHub (Jun 11, 2021).

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.

Originally created by @jazzdelightsme on GitHub (Jun 11, 2021). ### 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.
claunia added the Help WantedProduct-ConhostIssue-BugPriority-3Area-Interaction labels 2026-01-31 04:03:52 +00:00
claunia commented 2026-01-31 04:03:53 +00:00
Author
Owner
Copy Link

@jazzdelightsme commented on GitHub (Jun 11, 2021):

The conhost window is on my primary monitor, with the taskbar on the bottom... it's almost like part of conhost thinks the window size is equal to the workarea of the monitor before the taskbar got placed there (but the window chrome is fine).

@jazzdelightsme commented on GitHub (Jun 11, 2021): The conhost window is on my primary monitor, with the taskbar on the bottom... it's almost like part of conhost thinks the window size is equal to the workarea of the monitor before the taskbar got placed there (but the window chrome is fine).
claunia commented 2026-01-31 04:03:53 +00:00
Author
Owner
Copy Link

@jazzdelightsme commented on GitHub (Jun 11, 2021):

On today's repro, I noticed that it repro'ed for multiple fullscreen'ed conhost windows on the same monitor... and then, after another disconnect/reconnect cycle, they fixed themselves! (without me restoring/re-maximizing or otherwise twiddling the window state) I think this is more [circumstantial] evidence in favor of a "desktop recalc" fiddling with the work area of the monitor, and conhost getting juked/out-of-sync with reality.

@ekoschik what do you think?

@jazzdelightsme commented on GitHub (Jun 11, 2021): On today's repro, I noticed that it repro'ed for multiple fullscreen'ed conhost windows on the same monitor... and then, after another disconnect/reconnect cycle, they fixed themselves! (without me restoring/re-maximizing or otherwise twiddling the window state) I think this is more [circumstantial] evidence in favor of a "desktop recalc" fiddling with the work area of the monitor, and conhost getting juked/out-of-sync with reality. @ekoschik what do you think?
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-Interaction Help Wanted Issue-Bug Priority-3 Product-Conhost
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#14210
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?