Corrupted terminal output after window resized

[RoadToDream]

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.0

Other Software

No response

Steps to reproduce

1. Open Terminal from any folder such that primary prompt is longer than one line.
2. Enter any command and click enter.
3. Maximize Terminal window so primary prompt is arranged within one line.
4. Cursor will be off-position and overwrite my primary prompt.
5. Video attached below:

Recording.2023-03-24.110725.mp4

Expected Behavior

No response

Actual Behavior

Cursor will be off-position and overwrite my primary prompt.

[lhecker]

Do you have "AtlasEngine" enabled or disabled?

If you have it disabled, could you report what happens if you enable it?

[RoadToDream]

Hi @lhecker, yes I have tried enabling and disabling the new text renderer, also tested toggling Redraw entire screen and their combinations. All of them behaves the same. The issue seems to exist in any program using ConPTY like VS Code.

[RoadToDream]

Seems like Terminal can't calculate the correct position of cursor but taking col position from last finished command.
For example, if primary prompt breaks into two lines and the cursor is at col 10 after the ls command is executed, after resizing the window such that primary prompt is within one line, cursor will be positioned to col 10 disregarding the updated primary prompt.

[j4james]

Note that the terminal displays the cursor in the correct position immediately after the resize - it's only once you start typing that it moves to the wrong place. So I suspect this may be PowerShell or PSReadLine issue. Possibly the same underlying problem as PowerShell/PSReadLine#1456.

Also note that you don't get this in the cmd shell, or a bash shell, which is another reason to believe that PowerShell may be the source of the problem.

[RoadToDream]

Hi @j4james, thank you for pointing this out. I have tested on an environment that does not have PSReadLine installed. But still you may be right, this seems to be a Powershell issue not a Terminal issue, as I have not observed it in a cmd shell. I will leave this issue open for now and reach out to Powershell support and wait for their response.

[zadjii-msft]

Yea, I'd be sure that this is a PowerShell issue. Does this repro in a conhost.exe window with the same PowerShell setup?

Looks like the downstream issue is being tracked in PowerShell/PowerShell#19405

[RoadToDream]

Hi @zadjii-msft, yes for now I believe this is a PowerShell issue and I have submitted in their repo. I may close this ticket now. Thank you and everyone else helping analyze root cause for this issue.