Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
egvijayanand opened this issue Nov 12, 2021 · 3 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@egvijayanand
Copy link

egvijayanand commented 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.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 12, 2021
@egvijayanand egvijayanand changed the title Cursor position moves into to the content when Terminal window is maximized Cursor position moves into the content when Terminal window is maximized Nov 12, 2021
@zadjii-msft
Copy link
Member

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

@ghost
Copy link

ghost commented 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 ghost closed this as completed Nov 16, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 16, 2021
@egvijayanand
Copy link
Author

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.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants