There should be no dead zone on top of maximized terminal #8395

Closed
opened 2026-01-31 01:28:18 +00:00 by claunia · 3 comments
Owner

Originally created by @VFLashM on GitHub (May 21, 2020).

Description of the new feature/enhancement

When terminal is maximized, tabs cannot be switched if mouse is on top of the screen. There is a dead zone on top of the tab. There should be none.

It may sound weird, but it's a common UX pattern. When you want to switch to the tab using the mouse you bring the mouse all the way up, then only move it horizontally to choose the tab.

If there is a dead zone on the top pixel of the display, it helps no one, but makes it significantly harder to switch terminal tabs using the mouse.

For the record, it's a common problem for all apps providing tabbed interface and all major browsers do it right (as in make tabs clickable all the way up).

Proposed technical implementation details (optional)

Tab click zone should extend to the top of the terminal.

Originally created by @VFLashM on GitHub (May 21, 2020). # Description of the new feature/enhancement When terminal is maximized, tabs cannot be switched if mouse is on top of the screen. There is a dead zone on top of the tab. There should be none. It may sound weird, but it's a common UX pattern. When you want to switch to the tab using the mouse you bring the mouse all the way up, then only move it horizontally to choose the tab. If there is a dead zone on the top pixel of the display, it helps no one, but makes it significantly harder to switch terminal tabs using the mouse. For the record, it's a common problem for all apps providing tabbed interface and all major browsers do it right (as in make tabs clickable all the way up). # Proposed technical implementation details (optional) Tab click zone should extend to the top of the terminal.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:28:18 +00:00
Author
Owner

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

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #2541 for more discussion.

/dup #2541

This is also already in a PR - #5881

@zadjii-msft commented on GitHub (May 21, 2020): Thanks for the suggestion! Please make [sure to search for duplicates](https://github.com/microsoft/terminal/issues?q=is%3Aissue+maximized+space+is%3Aclosed) when filing new issues. This is already being tracked by another issue on our repo - please refer to #2541 for more discussion. /dup #2541 This is also already in a PR - #5881
Author
Owner

@ghost commented on GitHub (May 21, 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 21, 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!
Author
Owner

@ghost commented on GitHub (May 21, 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 21, 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#8395