<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: Win32NT 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2762.0"><pre lang="none" class="notranslate"><code class="notranslate">Windows build number: Win32NT 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2762.0
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<p dir="auto"><code class="notranslate">ssh</code> to a Linux box.</p>
<p dir="auto">Get Markus Kuhn's <a href="https://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-test.txt" rel="nofollow">UTF-8 decoder capability and stress test</a> file.</p>
<p dir="auto"><code class="notranslate">cat UTF-8-test.txt</code></p>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">Consistent output (which, by the way, reasonably closely matches what's described in the file), regardless of timing, including with various parameters to <a href="https://gitlab.gnome.org/GNOME/vte/blob/0.58.1/src/slowcat.c" rel="nofollow">slowcat</a>.</p>
<h1 dir="auto">Actual behavior</h1>
<p dir="auto">Faulty and inconsistent output, presumably depending on the timing of events.</p>
<p dir="auto">Often the output terminates way too prematurely, e.g. during the intro or section 1 or 2 of the file. Sometimes the succeeding shell prompt isn't printed either, although the shell is already ready to accept a new command.</p>
<p dir="auto">Other times the output ends as the end of the text file, but as you scroll back you'll notice that a big chunk is missing.</p>
<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Monitor 1: 3840x2160 (225%)
Monitor 2 (new default): 2560x1440 (125%)"><pre lang="none" class="notranslate"><code class="notranslate">Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Monitor 1: 3840x2160 (225%)
Monitor 2 (new default): 2560x1440 (125%)
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<ol dir="auto">
<li>Open Terminal and maximize its window</li>
<li>Attach a new default monitor to the device with a different scaling percentage from the previous one (the window is moved to the new monitor retaining its maximized state)</li>
<li><g-emoji class="g-emoji" alias="boom" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4a5.png">💥</g-emoji></li>
</ol>
<p dir="auto">It's easier to notice this if the new default monitor is placed on the left of the previous one.</p>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">The title bar is sized correctly.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/2650264/69074447-ae2ac280-0a2f-11ea-85f7-d7e5c097b4f4.png"><img src="https://user-images.githubusercontent.com/2650264/69074447-ae2ac280-0a2f-11ea-85f7-d7e5c097b4f4.png" alt="image" style="max-width: 100%;"></a></p>
<h1 dir="auto">Actual behavior</h1>
<p dir="auto">The title bar is wider than the actual window by 9px.<br>
Resizing the window fixes the width.</p>
<p dir="auto">This is a little annoying because the 9px grey area goes on to the next monitor and it does nothing when you click on it.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/2650264/69074384-8c314000-0a2f-11ea-9d74-353e7a0c9993.png"><img src="https://user-images.githubusercontent.com/2650264/69074384-8c314000-0a2f-11ea-9d74-353e7a0c9993.png" alt="image" style="max-width: 100%;"></a></p>