Clicking on already active tab header does not allow keystrokes #8304

Closed
opened 2026-01-31 01:26:04 +00:00 by claunia · 2 comments
Owner

Originally created by @chrjorgensen on GitHub (May 20, 2020).

When I click on the tab header when the tab is already active, any keystrokes are not sent to the terminal window.

This is especially annoying when the terminal app is out of focus and I want to switch to the app - I click on the tab header and start typing, but no keystrokes get to the pane as I would expect. But the problem also occurs when the terminal app is in focus and I click on the tab header of the active tab.

There should be no difference whether I click in the pane or on the tab header.

Environment

Microsoft Windows [Version 10.0.19041.264]
Windows Terminal Version: 1.0.1401.0

Steps to reproduce

Click on the tab header of the already active tab.

Expected behavior

Any keystrokes should be sent to the pane.

Actual behavior

No keystrokes are sent to the pane.

Originally created by @chrjorgensen on GitHub (May 20, 2020). When I click on the tab header when the tab is already active, any keystrokes are not sent to the terminal window. This is especially annoying when the terminal app is out of focus and I want to switch to the app - I click on the tab header and start typing, but no keystrokes get to the pane as I would expect. But the problem also occurs when the terminal app is in focus and I click on the tab header of the active tab. There should be no difference whether I click in the pane or on the tab header. # Environment ```none Microsoft Windows [Version 10.0.19041.264] Windows Terminal Version: 1.0.1401.0 ``` # Steps to reproduce Click on the tab header of the already active tab. # Expected behavior Any keystrokes should be sent to the pane. # Actual behavior No keystrokes are sent to the pane.
claunia added the Resolution-Duplicate label 2026-01-31 01:26:04 +00:00
Author
Owner

@zadjii-msft commented on GitHub (May 20, 2020):

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #3609 for more discussion.

/dup #3609 #6006

@zadjii-msft commented on GitHub (May 20, 2020): Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #3609 for more discussion. /dup #3609 #6006
Author
Owner

@ghost commented on GitHub (May 20, 2020):

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 (May 20, 2020): 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#8304