starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Can't drag the window using the pixels on top of the screen over a tab #7584

New Issue
Open
opened 2026-01-31 01:07:54 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:07:54 +00:00
Owner
Copy Link

Originally created by @JK3Farden on GitHub (Apr 23, 2020).

Environment

Windows build number: Microsoft Windows [version 10.0.18363.778]
Windows Terminal version (if applicable): 0.10.781.0

Steps to reproduce

  1. Maximize the terminal window
  2. Open a lot of tabs to fill the title bar
  3. Try to drag the window using the title bar, placing the mouse above one of the tabs (top of the screen)

Expected behavior

The window should un-maximize and begin to move with the mouse, just like every other window.

Actual behavior

The window doesn't move at all.

Originally created by @JK3Farden on GitHub (Apr 23, 2020). # Environment Windows build number: Microsoft Windows [version 10.0.18363.778] Windows Terminal version (if applicable): 0.10.781.0 # Steps to reproduce 1. Maximize the terminal window 2. Open a lot of tabs to fill the title bar 3. Try to drag the window using the title bar, placing the mouse above one of the tabs (top of the screen) # Expected behavior The window should un-maximize and begin to move with the mouse, just like every other window. # Actual behavior The window doesn't move at all.
claunia added the Issue-TaskProduct-TerminalArea-UserInterface labels 2026-01-31 01:07:54 +00:00
claunia commented 2026-01-31 01:07:55 +00:00
Author
Owner
Copy Link

@Zenexer commented on GitHub (Apr 23, 2020):

I'd actually rather that the tabs extend to the very top, just like most web browsers (tested in Chrome, Firefox, Edge). That would allow me to quickly select a tab by quickly moving my mouse to the top of the screen without worrying about overshooting on the vertical axis.

@Zenexer commented on GitHub (Apr 23, 2020): I'd actually rather that the tabs extend to the very top, just like most web browsers (tested in Chrome, Firefox, Edge). That would allow me to quickly select a tab by quickly moving my mouse to the top of the screen without worrying about overshooting on the vertical axis.
claunia commented 2026-01-31 01:07:55 +00:00
Author
Owner
Copy Link

@JK3Farden commented on GitHub (Apr 23, 2020):

Maybe we could have an option to get an actual title bar, therefore allowing both options.

@JK3Farden commented on GitHub (Apr 23, 2020): Maybe we could have an option to get an actual title bar, therefore allowing both options.
claunia commented 2026-01-31 01:07:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 23, 2020):

You know, I could have sworn we had a dupe for this one....

  • There's #2541, but that's specific to the "when maximized" scenario
  • In general, this is a hard problem because of the way we're architected with XAML Islands - we basically have to manually cut out the region around the tabs that should accept clicks. This might be more possible with #5485, but we'd basically need another HWND for the area above the tabs.
    • We'd probably also need to more carefully coordinate with where the tabs actually are in XAML - with #3327, we wouldn't be able to always know exactly how tall the tabs will be, we'd have to ask XAML for that.
  • @JK3Farden

    Maybe we could have an option to get an actual title bar

    We actually already have this option, try putting "showTabsInTitlebar": false in your global settings
@zadjii-msft commented on GitHub (Apr 23, 2020): You know, I could have sworn we had a dupe for this one.... * There's #2541, but that's specific to the "when maximized" scenario * In _general_, this is a hard problem because of the way we're architected with XAML Islands - we basically have to manually cut out the region around the tabs that should accept clicks. This might be more possible with #5485, but we'd basically need another HWND for the area above the tabs. - We'd probably also need to more carefully coordinate with where the tabs actually are in XAML - with #3327, we wouldn't be able to always know exactly how tall the tabs will be, we'd have to ask XAML for that. * @JK3Farden > Maybe we could have an option to get an actual title bar > We actually already have this option, try putting `"showTabsInTitlebar": false` in your global settings
claunia commented 2026-01-31 01:07:56 +00:00
Author
Owner
Copy Link

@JK3Farden commented on GitHub (Apr 23, 2020):

Well thank you for the "showTabsInTitlebar": false option, I didn't know about it. It solves my use case, but I think this issue might still be interesting to properly solve, one way or another. Having a dead row of pixels in the title bar doesn't seem like an intended behavior.

@JK3Farden commented on GitHub (Apr 23, 2020): Well thank you for the "showTabsInTitlebar": false option, I didn't know about it. It solves my use case, but I think this issue might still be interesting to properly solve, one way or another. Having a dead row of pixels in the title bar doesn't seem like an intended behavior.
claunia commented 2026-01-31 01:07:56 +00:00
Author
Owner
Copy Link

@morganwdavis commented on GitHub (Jul 18, 2022):

This Windows Terminal window is partially visible.

image

The frame area above the tabs is useless except for a tiny area, but only if you can move the window into view so you can access it.

image

Dragging on that area above the tabs to move the window would solve this. I had to use keyboard shortcuts to fully zoom the window to get control of it. I understand this is a challenge, but consider this a vote for it.

@morganwdavis commented on GitHub (Jul 18, 2022): This Windows Terminal window is partially visible. ![image](https://user-images.githubusercontent.com/4434533/179433813-3697ee73-66b5-4bc3-9964-43825520858f.png) The frame area above the tabs is useless except for a tiny area, but only if you can move the window into view so you can access it. ![image](https://user-images.githubusercontent.com/4434533/179434000-74798344-7cef-4ac1-af2c-2a5c38b52d29.png) Dragging on that area above the tabs to move the window would solve this. I had to use keyboard shortcuts to fully zoom the window to get control of it. I understand this is a challenge, but consider this a vote for it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-UserInterface Issue-Task Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7584
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?