Description of the issue:
Ever since V1.30.86 Brave now opens with what seems like an rather giant invisible border (seems it’s including drop shadow [and ignoring UI/WM settings for drop shadows] as window dimension) or window decoration. When I say “invisible” I don’t mean it’s there and can be interacted with it’s just a way to say there is a rather uniform border around the windows that then cause the actual size of the window to be wrong and requires constant resizing.
So I got fed up with this and decided to add some wmctrl to my session script to fix this bs. What I’ve found is I have to set the windows -10 to get it to the top of my screen +41 taller than my screens height to get it to go to the bottom and +34 wider than they should be to get the correct width.
I think you might have better luck getting some help here if you give us a few more specifics about your system than “linux”…ubuntu? debian?
I’ve got v1.31.87 installed on my lubuntu 20.04 machine and that issue disappeared a few updates ago…
I can confirm this issue. Running Xubuntu 21.10. The issue occurs with GTK+, classic and designs downloaded from Chrome Extensions. Worse yet, maximizing the window in XFCE now renders the browser window beyond the screen dimensions, meaning the tab bar extends into the task bar at the top and the window corners are cut off. This never happened with any of the previous Brave versions I used.
I can confirm this on v1.31.87(after update) on Manjaro xfce(linux). I have GTK+ theme enabled. Same issue as @Valsu. Also part of left and right sides are cut off for me. Scroll bar is invisible.
Indeed, maximizing goes off screen, it’s like it’s adding the window shadows as the dimensions. More so it’s also ignoring UI preferences about BS like window drop shadows.
Perhaps the XFCE theme has some influence? For me it’s working fine after enabling this option. I’m using Equilux-Compact for Desktop Style and Window Manager. Maximize and minimize are respecting the window borders and dragging and snapping are working fine as well.
It depends on the underlying issue. In the other threads with this similar problem with XFCE, Chromium 95 and Chrome 95 are also affected as it appears to have been traced to a Chromium 95 bug.
If this doesn’t affect either of those then it could be a different issue.