macOS Fullscreen: Top Title Bar Covers Tabs When Hovering Too Far Up

Description:
When using Brave in fullscreen mode on macOS, if I hover near the top bar area where the tabs are displayed, moving the mouse pointer slightly further up causes the top window bar (with close, minimize, and maximize buttons) to slide down and cover the entire tabs bar. This interrupts browsing and makes switching between tabs difficult.

Steps to Reproduce:

  1. Open Brave browser on macOS.

  2. Enter fullscreen mode (using the green maximize button or fullscreen shortcut).

  3. Hover the mouse near the top edge of the screen over the tabs bar.

  4. Move the mouse slightly further upward.

  5. Observe the top macOS title bar dropping down and covering the tabs area.

Expected Result:
The top bar with window controls should either be embedded within the tab bar or not obstruct the tabs when hovering near the screen top in fullscreen.

Actual Result:
The macOS top title bar floats over and covers the tabs bar, making it difficult to access or switch tabs while in fullscreen.

Frequency:
Consistently reproducible every time in fullscreen mode.

Brave Version:
1.83.120 Chromium: 141.0.7390.122 (Official Build) (arm64)

Operating System:
macOS 26.1

Additional Notes:
This behavior is a regression compared to other browsers (like Safari or Chrome) on macOS, where window controls are integrated within the tabs area in fullscreen mode, ensuring better usability.

This has been talked about a bit recently … I think… I’ve been trying to find some GitHub Issues & Community Topics, this is what I’ve found:
macos :

Recently on Community: Fullscreen Mode Issues on MacOS - #10 by yurakgn
&
@dekramer123: Mac fullscreen is nearly unusable since this change

less to do with windows but maybe somewhat related:

Recently on Community: Address bar and other controls to full screen mode - #10 by Mattches

@Mattches if you could take a look at this again when you can (Please & Thank You), particularly with what @dekramer123 pointed out in his post (again here) that Chrome is fixed but not Brave and those GitHub issues are saying it’s an upstream Chrome thing… if I’m reading things correctly :man_shrugging:

(I personally don’t use Fullscreen and/or Chrome so didn’t check things myself, and so it’s not an issue for me, just thought I’d point it out for others)

Also @cna_ch since it is Sunday at time of writing this, we’ll still need to wait until Monday/tomorrow at the earliest for a response from Brave Employees/Support :wink:

Yeah thanks for pointing this out. Not sure why we didn’t get the same fix as Chrome did. Let me ask some devs about this as we should be following the same behavior.

1 Like

I wanted to take a moment to thank you for your prompt and helpful response to my request. Your support has been invaluable, and I truly appreciate the effort you put into resolving the issue. Thank you again for your excellent service!

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.