starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Cursor position moves into the content when Terminal window is maximized #15859

New Issue
Closed
opened 2026-01-31 04:50:35 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:50:35 +00:00
Owner
Copy Link

Originally created by @egvijayanand on GitHub (Nov 12, 2021).

Windows Terminal version (or Windows build number)

Terminal: 1.11.2921.0
Windows: 10.0.22000.318

Other Software

No response

Steps to reproduce

Open the Windows Terminal in the default-sized window and run any command which returns a good amount of content as its output like dotnet new blazorwasm --help so that it takes up some screen space.

Run the command and then maximize the Terminal window, the cursor position jumps into somewhere in the output content of the previous command rather than in a new blank line.

Refer to the below screenshot for visual representation, the current cursor position is highlighted.

Windows-Terminal-Window-Resize-Cursor-Issue

Expected Behavior

The cursor position should stay in the current blank line even when windows get resized (maximize, manul resizing).

Actual Behavior

The cursor position moves into the output content of the previous command.

Originally created by @egvijayanand on GitHub (Nov 12, 2021). ### Windows Terminal version (or Windows build number) Terminal: 1.11.2921.0 Windows: 10.0.22000.318 ### Other Software _No response_ ### Steps to reproduce Open the Windows Terminal in the default-sized window and run any command which returns a good amount of content as its output like `dotnet new blazorwasm --help` so that it takes up some screen space. Run the command and then maximize the Terminal window, the cursor position jumps into somewhere in the output content of the previous command rather than in a new blank line. Refer to the below screenshot for visual representation, the current cursor position is highlighted. <img width="960" alt="Windows-Terminal-Window-Resize-Cursor-Issue" src="https://user-images.githubusercontent.com/81947404/141455920-051ac2f5-e9de-4499-aefc-196a122f5f4c.png"> ### Expected Behavior The cursor position should stay in the current blank line even when windows get resized (maximize, manul resizing). ### Actual Behavior The cursor position moves into the output content of the previous command.
claunia added the Resolution-Duplicate label 2026-01-31 04:50:35 +00:00
claunia commented 2026-01-31 04:50:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 16, 2021):

THAT IS A VERY CONSISTENT REPRO FOR THIS BUG!

THANK GOD!

I've been looking for a consistent repro for months. This is a great thing to have. The bugger picture is #5800, but I think #7253 is specifically the same root cause as this. I'm gonna move this repro there. Thanks!

/dup #7253

@zadjii-msft commented on GitHub (Nov 16, 2021): THAT IS A VERY CONSISTENT REPRO FOR THIS BUG! THANK GOD! I've been looking for a consistent repro for _months_. This is a great thing to have. The bugger picture is #5800, but I think #7253 is specifically the same root cause as this. I'm gonna move this repro there. Thanks! /dup #7253
claunia commented 2026-01-31 04:50:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 16, 2021):

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!

@ghost commented on GitHub (Nov 16, 2021): 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!
claunia commented 2026-01-31 04:50:37 +00:00
Author
Owner
Copy Link

@egvijayanand commented on GitHub (Nov 16, 2021):

Glad to know at least it helped to repro the issue in a consistent way.

Hope a fix will be made available at the earliest.

@egvijayanand commented on GitHub (Nov 16, 2021): Glad to know at least it helped to repro the issue in a consistent way. Hope a fix will be made available at the earliest.
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 Resolution-Duplicate
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#15859
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?