when using telnet in windows terminal, the mouse wheel can not work #16731

Closed
opened 2026-01-31 05:21:07 +00:00 by claunia · 3 comments
Owner

Originally created by @baalchina on GitHub (Feb 10, 2022).

Windows Terminal version

1.12.10334.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

Hi, when I using telnet connect to a switch, in windows terminal , after the page scroll down, I can not using mouse wheel to scroll up, so many output I can not see because they disappear.
But when I using telnet in cmd.exe , the wheel can work.
So, it this a bug or a config issue? Thanks.

Expected Behavior

No response

Actual Behavior

Hi, when I using telnet connect to a switch, in windows terminal , after the page scroll down, I can not using mouse wheel to scroll up, so many output I can not see because they disappear.
But when I using telnet in cmd.exe , the wheel can work.
So, it this a bug or a config issue? Thanks.

Originally created by @baalchina on GitHub (Feb 10, 2022). ### Windows Terminal version 1.12.10334.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce Hi, when I using telnet connect to a switch, in windows terminal , after the page scroll down, I can not using mouse wheel to scroll up, so many output I can not see because they disappear. But when I using telnet in cmd.exe , the wheel can work. So, it this a bug or a config issue? Thanks. ### Expected Behavior _No response_ ### Actual Behavior Hi, when I using telnet connect to a switch, in windows terminal , after the page scroll down, I can not using mouse wheel to scroll up, so many output I can not see because they disappear. But when I using telnet in cmd.exe , the wheel can work. So, it this a bug or a config issue? Thanks.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:21:07 +00:00
Author
Owner

@j4james commented on GitHub (Feb 10, 2022):

This sounds like it might be the same thing as #6056.

@j4james commented on GitHub (Feb 10, 2022): This sounds like it might be the same thing as #6056.
Author
Owner

@zadjii-msft commented on GitHub (Feb 10, 2022):

This is most definitely /dup #6056

@zadjii-msft commented on GitHub (Feb 10, 2022): This is most definitely /dup #6056
Author
Owner

@ghost commented on GitHub (Feb 10, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 10, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16731