Weird string value written to the standard output

Unwanted std out side effect on window resize The library (or one of its dependencies?) seems to write the string value “\u001b[3J” to the standard output under certain circumstances. As a result, if one has decided to redirect the standard output to some UI component, such as a TextView, they see this weird string value the first time the application starts and whenever the window size changes.

To Reproduce Steps to reproduce the behavior:

1. Create a console GUI app with a multiline text view (the component and its multiline attribute should be irrelevant).
2. Redirect the standard output like so: Console.SetOut(outputWriter); where outputWriter is a TextWriter that writes to the text view.
3. Start the application and observe the the weird string value written to the text view.
4. Resize the window or enter and exit full screen and observe the same value written multiple times.

Expected behavior This string value should not be written to the standard output.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10

[BDisp]

Ok no problem. For your information there are 3 official drivers and another for tests (FakeDriver).

If you are running on a Windows OS:

• If you running with the Application.UseSystemConsole as false (default) then you are using the WindowsDriver.
• If you running with the Application.UseSystemConsole as true then you are using the NetDriver.

If you are running on a Linux or macOS:

• If you running with the Application.UseSystemConsole as false (default) then you are using the CursesDriver.
• If you running with the Application.UseSystemConsole as true then you are using the NetDriver.

So the NetDriver is a cross platform driver but more slower.

[BDisp]

I already expected that. Was changed from “\u001b[3J” to “\u001b[0J”. This code is in the ResizeScreen method of the WindowsDriver.cs. Removing it solves the issue. That PR is still under development, I think. WindowsDriver can not have escape sequences because it isn’t configured to use virtual terminal, so it’s supposed to output that characters if the console output is redirected, on theses terminals (cmd, vsdebugger, conhost, pwsh). Strangely the escape sequences are executed on the Windows Terminal but, unfortunately still have some incompatibilities with legacy terminal, like not allowing resize the console buffer size but only the window size.