Cannot scroll in terminal window created by api until resize

[DonJayamanne]

From @hun1ahpu on February 12, 2017 10:22

Environment data

VS Code version: 1.9.1
Python Extension version: 0.5.8
Python Version: 3
OS and version: win 10

Actual behavior

Mouse wheel scroll doesn't work
Scroll bar is not visible
After resizing the terminal window it starts working

Steps to reproduce:

• Open any python file and execute any line of it

Copied from original issue: DonJayamanne/pythonVSCode#739

[daviwil]

Ahhh! I'm seeing this too in the PowerShell extension. I thought it was something I was doing wrong :)

[jsk01]

The scrollbar now seems to work correctly in the insiders build when using powershell.

[Tyriar]

@jsk01 this bug was a little flaky, I don't think any changes were made in this area.

[gandhis1]

Strangely enough, I used to not get this bug, but now I do on the latest official release. I get this behavior with a Python file that is executing in the terminal - I cannot use the mouse scroll button to scroll the terminal, nor is there a scroll bar that I can click on available. However, once I use the resize arrow or actually drag to resize, the scrolling begins to work. It's quite annoying

[stayfool]

This problem is ok in windows 10.

[KillyMXI]

Windows 10 Pro (v 1607), VS Code 1.12.2

The issue still exists.
The first opened terminal works as intended (with scroll). All the next terminal sessions will have no scroll until resized or VSCode restarted.

[shmutalov]

Very annoying issue -_-
VSCode 1.13.1, Windows 10 x64
https://www.youtube.com/watch?v=6ZsStclrirg

[chrmarti]

@Tyriar Can reproduce with Python's 'Run Selection' command on Windows. Logging this.charMeasure.height in Viewport.refresh() shows that charMeasure isn't initialized in time.

[Tyriar]

Sat together with @chrmarti yesterday to figure this thing out, the fix for this is coming in 1.15 🎉

It was an obscure bug that was happening when the terminal was created before the panel was shown. It was caused by eb85ea8 to fix #22328. The reason is because since we were not setting the pty and xterm.js to the correct size before the terminal existed, xterm.js didn't bother doing a proper resize and the adjustments necessary (like re-measuring the character size) here https://github.com/sourcelair/xterm.js/blob/85c892c218c5529efd01569b7dc9b1123ae53582/src/xterm.js#L1942

[shmutalov]

@Tyriar good to hear that 🐱