VT color displayed on Windows Terminal leaks to the rest of line when resizing the terminal window

[daxian-dbw]

Windows Terminal version (or Windows build number)

1.12.2931.0

Other Software

This is not related to the application that uses Windows Terminal. You can reproduce this with bash in WSL or PowerShell.

Steps to reproduce

In PowerShell, do the following:

1. Run "`e[44;1mYEAH YEAH YEAH YEAH`e[0m"
2. Resize the window
3. The color gets leaked to the rest of line

Similar in bash in WSL:

Expected Behavior

Given that the string written out ends with ESC[0m to unset all attributes, the color should not leak to the rest of line when resizing window.

Actual Behavior

The color gets leaked to the rest of line when resizing happens.

[elsaco]

@daxian-dbw alacritty does it also:

[daxian-dbw]

The leak doesn't happen when I do the same on macOS or Ubuntu:

PowerShell adopts colors in its formatting, but when there is any resize of the window, the background color will be leaked to rest line and make it look really bad. It would be nice to fix this in Windows Terminal.

[j4james]

I'm afraid this is a known problem. Second oldest open issue in the repo actually. See #32.

Technically that's tagged as a conhost issue, but that's only because it was a couple of year before Windows Terminal was even released. I'm fairly certain the underlying cause is the same in both conhost and WT.

[daxian-dbw]

Thanks @j4james, I didn't find that issue before opening this one. Maintainers can close this one as a duplicate.
It's a little disappointing to see #32 is marked with "Priority-3". Wish it can be addressed sooner.

[zadjii-msft]

/dup #32

It's a little disappointing to see #32 is marked with "Priority-3". Wish it can be addressed sooner.

Alas, it's a combination of "It's a hard bug to fix" combined with "it's not that impactful". If anyone's got clever ideas of how to solve that, we're all ears! We suspect it'll just get better when #8000 is finished as well, though it's anyone's guess when that'll be done.

[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!