[BUG] Top padding above tabs on Edge Chromium maximized window doesn't get hidden (macOS only)

[nomad1215]

As you can see from the image attached, there is unnecessary spacing above the tabs in maximized and fullscreen mode in macOS (v10.14.6). Edge in Windows-OS doesn't seem to be affected by this as the padding is removed when the Edge window is maximized (tested in Windows 10). This I assume is a bug. If not please consider this as feedback and add an option in Edge's preference to remove the padding regardless of the window size/mode.

There is an option to remove this padding on some browsers including Firefox on any window size, which keeps things minimal. Currently, Edge looks like a touch-friendly version of Google Chrome with those tall UI elements which take prominence over the webpage/content.

Thanks :)

Stay Safe.

[#2]

@nomad1215 Thanks for reporting that! I'll reach out to our mac team and loop them in.

In the meantime, can you please submit feedback, diagnostics, and a screenshot through the browser if you haven't yet? It helps the team nail down the bug.

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

[#3 · Accepted solution]

Thanks @nomad1215. This is Aditya, Product Manager on Edge on Mac. We have marked this open for investigation and will get back if this needs to be changed or with the reasoning for the current behavior. Thanks for reporting this.

[#4]

Hi @aditya10, any update on this issue?
I resently started using Edge mac version.

It seems that the issue haven't been fixed?

[#5]

@cchen1290Even worse, it's now present also on Win10. Extremely annoying, in my experience 30% of my tab clicks miss the actual tab.

[#6]

Any update on this? Edge is exhibiting the same behavior on Windows as well. There is unnecessary padding when Edge is open in windowed mode that goes away in full screen. This makes it difficult to accurately click on the tab.

[#7]

Hello @aditya10  Any update on this?
It is end of 2023 and I am still seeing this issue. I am using Windows 10.

[#8]

Hi ,
Do we have a fix for this, it seems an issue that was addressed 3 years back is still on going.
Give an answer either there is a solution for this or not or Micorosft it self not able to replicate this issue ?