Terminal keeps scrolling up when typing, leaving a mostly blank panel.

[garretwilson]

I have a keypress mapped to the workbench.action.toggleMaximizedPanel when in terminalFocus, so that my terminal will vertically fill VS Code so that I can see all the terminal output. Unfortunately VS Code thwarts my efforts, because as soon as I start typing, it scrolls the terminal content up, leaving about 2/3 of the bottom half of the terminal as blank space!

I'll use my mouse scroll back to the terminal history so that I can see what the terminal output was before. The cursor will still be visible at the bottom of the panel. I'll happily start to type, looking at the previous terminal history at the top of the panel. But as soon as I press a key, VS Code scrolls everything up, hiding the history again.

This happens for no reason, as the cursor is visible in the panel, and even has blank space below it. There is no reason to scroll the terminal up under these conditions. It's very irritating and gets in the way of productivity.

Version: 1.105.1 (user setup)
Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

[meganrogge]

I'm not sure what you mean. Maybe a gif would help?

[garretwilson]

Here is my terminal panel, filling the application vertically because I used the workbench.action.toggleMaximizedPanel command:

+-----+
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
+-----+

Note the ..., indicating text. I can see the terminal history of the commands I've entered and their output. As soon as I type any key, VS Code scrolls the history up for no reason, leaving me with this.

+-----+
|.....|
|.....|
|.....|
|     |
|     |
|     |
|     |
|     |
|     |
+-----+

I can no longer see my history. So I scroll it back down:

+-----+
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
|.....|
+-----+

But as soon as I type another key, VS Code scrolls it back up again:

+-----+
|.....|
|.....|
|.....|
|     |
|     |
|     |
|     |
|     |
|     |
+-----+

[meganrogge]

I cannot reproduce, so will need a gif.

[garretwilson]

I don't have my GIF-maker handy. Why don't you post a GIF of your not reproducing it, and I'll tell you how your steps to reproduce it do not match.

[meganrogge]

https://gifcap.dev/

[garretwilson]

I cannot reproduce …

I've found an easy way for you to reproduce this with step-by-step instructions. It happens with commands that produce a lot of output when the terminal panel is maximized. It would appear that VS Code incorrectly "remembers" the small size of the terminal before it was maximized.

Follow these steps.

1. Open a directory/workspace.
2. Open the terminal. Ensure that the terminal is in non-maximized mode (i.e. at the bottom of the screen) and in Bash.
3. Execute this Bash command: seq 1 1000
4. Invoke the VS Code command workbench.action.toggleMaximizedPanel (View: Toggle Maximized Panel). The panel will suddenly look like this:

   +-----+
   |.....|
   |.....|
   |.....|
   |     |
   |     |
   |     |
   |     |
   |     |
   |     |
   +-----+
   

5. Already you can suspect there might be a problem, because there was no need to have added all that blank space. Now scroll the history back so that you can see the earlier numbers it printed:

   +-----+
   |.....|
   |.....|
   |.....|
   |.....|
   |.....|
   |.....|
   |.....|
   |.....|
   |.....|
   +-----+
   

6. Now type any key on the keyboard. (x will do nicely.) VS Code will scroll the history back up, leaving a huge amount of blank space:

   +-----+
   |.....|
   |.....|
   |.....|
   |     |
   |     |
   |     |
   |     |
   |     |
   |     |
   +-----+
   

You should have reproduced the issue at this point.

(This especially gets in the way on a large monitor. Please don't try to reproduce this on a 1024 x 768 monitor, for example.)

[garretwilson]

Can you provide an update on this? I have provided simple, detailed steps for reproducing. Can you at least acknowledge the issue and provide an indication of when it could be addressed? Feedback to a paying customer would be welcome here. Thank you.

[meganrogge]

Cannot reproduce, thus closing.

demo.mov