Why does maximize use the auto-hide titlebar?

%3CLINGO-SUB%20id%3D%22lingo-sub-2931639%22%20slang%3D%22en-US%22%3EWhy%20does%20maximize%20use%20the%20auto-hide%20titlebar%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2931639%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20always%20been%20curious%20-%20why%20on%20Mac%20does%20Edge's%20maximize%20implementation%20use%20an%20auto-hide%20titlebar%2C%20z-ordered%20on%20top%20of%20the%20tabs%2C%20rather%20than%20inlining%20the%20window%20controls%20to%20the%20left%20of%20the%20tabs%2C%20as%20it%20does%20when%20unmaximized%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20the%20auto-hide%20titlebar%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22WadeDorrell_0-1636124117028.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F324582iAC8C934E353FBE00%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22WadeDorrell_0-1636124117028.png%22%20alt%3D%22WadeDorrell_0-1636124117028.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EI%20find%20this%20behavior%20makes%20mousing%20to%20switch%20tabs%20difficult%20-%20if%20you%20overshoot%20the%20tabs%2C%20into%20the%20menu%20area%2C%20then%20the%20titlebar%20covers%20the%20tabs%2C%20and%20you%20have%20to%20overshoot%20again%2C%20to%20below%20the%20tabs%2C%20to%20dismiss%20it%2C%20before%20you%20can%20you%20can%20try%20again.%20Feels%20like%20I%20could%20be%20more%20efficient%2C%20the%20app%20interface%20less%20%22chatty%22%2C%20if%20Edge%20didn't%20do%20this%2C%20and%20I'm%20curious%20why%20it's%20this%20way!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(There%20are%20definitely%20a%20lot%20of%20Mac%20apps%20that%20use%20the%20same%20auto-hide%20titlebar%20-%20but%20the%20ones%20that%20have%20meaningful%20user%20interface%20at%20the%20top%20edge%20of%20windows%20-%20Finder%2C%20for%20example%20-%20tend%20to%20inline%20the%20window%20controls%2C%20as%20I%20suggest%20Edge%20could%20do.%20And%20I%20suppose%20this%20didn't%20used%20to%20be%20a%20big%20deal%20until%20Spaces%20made%20maximized%2Ffull-screen%20the%20same%20thing%20by%20default.)%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I'm curious - why, on Mac, does Edge's maximize implementation use an auto-hide titlebar, z-ordered on top of the tabs, rather than giving the window controls a permanent spot left of the tabs, as when unmaximized?

 

Here's the auto-hide titlebar, covering the tabs:

 

WadeDorrell_0-1636124117028.png

The auto-hide UI makes mousing to switch tabs difficult - when moving up, if I overshoot the tabs a bit, then the titlebar covers them, and I have to overshoot down dismiss it, before trying again. Feels like I could be more efficient, the app interface more accessible and less "chatty", if Edge didn't do this, and I'm curious if there's a strong reason it needs to stay as it is.

 

There are many Mac apps that use the same auto-hide titlebar - but the apps that have meaningful user interface at the top edge of windows, Finder, for example, give the window controls a permanent position on the left, as I suggest Edge could do. (I'm not sure what the Office team's doing auto-hiding the controls themselves - which causes the "quick action" buttons to move horizontally if you overshoot them - please don't follow that example! A permanent position for buttons is the ideal.)

 

I suppose this didn't used to be a big deal until Spaces changed how maximize works - before that full-screen modes like Chrome/Edge's were an exception rather than the rule.

0 Replies