Terminal reports no longer work in Vttest #14208
Description
Windows Terminal version
Commit cacf668
Windows build number
10.0.19044.2006
Other Software
Vttest
Steps to reproduce
- Open a WSL shell in conhost or Terminal
- Run
vttest. - Select the Private Device Attributes test (menu 6.4).
Expected Behavior
The report received from the terminal should be:
<27> [ ? 1 ; 0 c
Actual Behavior
In conhost it only seems to receive the initial ESC character, while in Terminal it receives nothing at all. And it's not just DA - other reports fail in a similar way.
I think this regression was caused by the recent DECARM merge (PR #13981), but I have no idea why. I'm still investigating.
The weird thing is that it works correctly in all of my own tests and applications. There's just something about the way vttest is reading the input that is causing it to fail.