Terminal: Can't drag the window using the pixels on top of the screen over a tab

[JK3Farden]

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.

[Zenexer]

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.

[JK3Farden]

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

[zadjii-msft]

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

[JK3Farden]

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.