Media and other keys autoscroll the terminal #7422

Open
opened 2026-01-31 01:03:35 +00:00 by claunia · 5 comments
Owner

Originally created by @tgross35 on GitHub (Apr 15, 2020).

Description

Keys that aren't meant to insert characters seem to jump the terminal to the bottom where input is being awaited. This includes media buttons.

Steps to reproduce

Open any terminal tab (tested with both Ubuntu and Powershell) and run anything to fill up the screen (e.g. run ls 5 times). Scroll up until the text input area is off the page.

Press any non-typing character that isn't a modifier (tested with "calculator" key, play/pause, and volume control keys)

Expected Behavior

These keys should have no effect on terminal

Actual behavior

Terminal scrolls to the bottom of the page where a new line is

ezgif-7-c7e99acf7c07

In this video I press the mute key or the calculator key, causing the terminal to jump

Version Info

Windows Terminal
Version: 0.10.781.0

Originally created by @tgross35 on GitHub (Apr 15, 2020). # Description Keys that aren't meant to insert characters seem to jump the terminal to the bottom where input is being awaited. This includes media buttons. # Steps to reproduce Open any terminal tab (tested with both Ubuntu and Powershell) and run anything to fill up the screen (e.g. run `ls` 5 times). Scroll up until the text input area is off the page. Press any non-typing character that isn't a modifier (tested with "calculator" key, play/pause, and volume control keys) # Expected Behavior These keys should have no effect on terminal # Actual behavior Terminal scrolls to the bottom of the page where a new line is ![ezgif-7-c7e99acf7c07](https://user-images.githubusercontent.com/13724985/79384807-8d5e8e80-7f35-11ea-943a-c395332eff09.gif) In this video I press the mute key or the calculator key, causing the terminal to jump # Version Info Windows Terminal Version: 0.10.781.0
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 17, 2020):

Yeah, that's a fair pull. We should only scroll on "input" if there actually was input.

@DHowett-MSFT commented on GitHub (Apr 17, 2020): Yeah, that's a fair pull. We should only scroll on "input" if there actually was input.
Author
Owner

@Decimation commented on GitHub (Nov 17, 2022):

Any updates on this? This is still a problem on the latest version.

@Decimation commented on GitHub (Nov 17, 2022): Any updates on this? This is still a problem on the latest version.
Author
Owner

@zadjii-msft commented on GitHub (Nov 17, 2022):

Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?
image
That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️

@zadjii-msft commented on GitHub (Nov 17, 2022): Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button? ![image](https://user-images.githubusercontent.com/18356694/91237459-5cbb0c80-e700-11ea-9347-b9b1ec2813b1.png) That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺️
Author
Owner

@squarestopsthere commented on GitHub (Dec 20, 2024):

This is also happening to me when clicking within a PowerShell window to highlight text.

@squarestopsthere commented on GitHub (Dec 20, 2024): This is also happening to me when clicking within a PowerShell window to highlight text.
Author
Owner

@lhecker commented on GitHub (Nov 25, 2025):

Pretty sure this is due to the IsInputKey function. It needs to be swapped to a whitelist, or we need to add the volume vkey. Tagged it up for 1.26, because it's probably easy to fix.

@lhecker commented on GitHub (Nov 25, 2025): Pretty sure this is due to the `IsInputKey` function. It needs to be swapped to a whitelist, or we need to add the volume vkey. Tagged it up for 1.26, because it's probably easy to fix.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7422