Powershell 6 resizing issues

[sbenalohm]

Environment

Windows build number: Microsoft Windows 10.0.18363
Windows Terminal version (if applicable): 0.7.3451.0

Any other software?
PowerShell Core 6.2.3

Steps to reproduce

Run PowerShell Core 6.2.3 in Windows Terminal, resize the window in any manner.

Expected behavior

The terminal prompt and existing printed text will be resized (i.e. line wrapping) and realigned to put the active prompt at the bottom of the window or at the lowest line if there aren't enough history lines to fill up the window.

All profiles other than PS6 (WSL, CMD, original PowerShell, Azure Cloud Terminal) are working fine in this regard, as well as the default PS6 terminal (not running it in Windows Terminal).

Actual behavior

The text stays in the same place relative to the border dimensions that the terminal/tab was instantiated with.

When the window is enlarged, all visible text remains inside the smaller original borders. See that in the 2nd image the output of the top command is cut off even though there is empty space below the last prompt line. Prompt lines will never fill this empty space.

If a new tab is opened once the window is larger, these new dimensions are accurately rendered with the new terminal tab. See how there is now no empty space below the last prompt.

When the window is made smaller, the printed text remains in the larger original borders making the current line (the cursor/new text) not visible as it remains outside the new smaller bounds. In the first image below I've typed a bogus command into the prompt, but it is not visible as it is a few lines below the bottom of the resized window. After hitting enter a few times, the 2nd image shows that the command ran, but was not visible in the terminal until enough new lines pushed it up into the view of the resized window.

[DHowett-MSFT]

Thanks for the detailed report! This seems like a /dupe of #1465

[ghost]

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!