Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.
Delete the any text above the line separator below before posting
Description of the issue: When I have Brave browser in full screen mode, very often the CMD+T shortcut to open a new tab in Mac OS does not do anything. For what it’s worth, I have multiple windows of Brave opened (each with multiple tabs). However, even when I’ve clicked within the window of Brave I’d like to open a new tab in, the keyboard shortcut usually does not work.
How can this issue be reproduced?
I don’t know?
Expected result: The keyboard shortcut (CMD+T) to open a new tab in a full screened window of Brave should open a new tab.
@ijaaji,
What’s strange here is that the behavior isn’t consistent. I’m wondering if there is maybe an extension that is conflicting with the keystroke for some reason or if a specific site(s) you have open is causing the conflict. For me, Cmd + T opens a new tab when viewing the browser in full screen mode, with or without the toolbar visible:
Can you try the following tests?
Try closing all browser windows except for one, then test opening a new tab in full screen and see if having multiple windows open is the cause of the issue (it shouldn’t, but good to check)
Launch Brave and create a new/fresh browser profile (Menu --> more tools --> Add profile), close any other Brave windows you have open (so that you only have the one window with the new profile open), then test the behavior again and see if the issue persists in the new profile
The scenario is as follows: MacBook with one Brave window open (not full-screened) connected to an external display with an additional Brave window in full screen mode. When this happens, the full screen Brave window on the external display sometimes will not allow me to open another tab w/ the cmd+T shortcut. It doesn’t happen every time, but something about this scenario yields that result.
Just tested this and still cannot repeat. It’s really hard to test/diagnose issues that happen only “sometimes” or “randomly”. I will ask folks on our macOS to try and repro the issue with the steps above regardless