You are not logged in.
So I ran a full system upgrade, and the left and right window borders are now transparent, leaving a space between the window border and the actual content.
Here is how it looks like:
I'm running BSPWM as my window manager. Although I'm using a script for drawing the double borders, ignoring it doesn't solve the issue either.
When Picom is not running, the space between the border and the content is black.
What troubles me the most is that the hitboxes are offset, I mean, if you were to click the search bar for example, you would have to move your cursor a little bit higher in order to actually click it.
It is also worth noting that when I check off the recommended performance settings, the issue moves to the bottom and right borders.
Firefox version: 137.0.1 (64-bit)
Last edited by nasp (2025-04-09 17:04:33)
Offline
You'll need to run a compositor -- like picom for a good standalone option, otherwise most GTK tools will start to have this border as GTK expects a compositing window manager.
Online
I have exactly the same problem. I run picom but the problem wont go away, even with shadows disabled.
Offline
I have the same problem. Not only on firefox 137 but also on librewolf and other forks and thunderbird. Compositor doesn't matter for me. I have tried chaning picom config and some picom forks but it didnt change a bit. Also i have tried xcompmgr but to no avail. Fot the record i use dwm.
Last edited by jawor (2025-04-11 19:15:13)
Offline
I've fixed this issue by changing in about:config
browser.tabs.inTitlebar from 0 to 2
and by moving from gtk2 to gtk3 with my theming
Offline
I've fixed this issue by changing in about:config
browser.tabs.inTitlebar from 0 to 2
and by moving from gtk2 to gtk3 with my theming
Really? browser.tabs.inTitlebar = 2 is the default in my browser. Though I'm curious about what you did with your theming and how it solved your issue.
Offline
Looks like an old gtk bug. Some patches have been submitted already.
https://github.com/baskerville/bspwm/issues/1524
https://gitlab.gnome.org/GNOME/gtk/-/me … uests/8423
https://bugzilla.mozilla.org/show_bug.cgi?id=1958174
Last edited by igrmm (2025-04-12 18:04:42)
Offline
jawor wrote:I've fixed this issue by changing in about:config
browser.tabs.inTitlebar from 0 to 2
and by moving from gtk2 to gtk3 with my themingReally? browser.tabs.inTitlebar = 2 is the default in my browser. Though I'm curious about what you did with your theming and how it solved your issue.
I mean i had this and i have used qt5gtk2 for theming and then i completely stopped using anything that had to do with gtk2 when it comes to theming
Offline
The bug is fixed with this gtk3 commit https://gitlab.gnome.org/GNOME/gtk/-/me … uests/8423 but a new version of gtk3 with the fix was not released yet. You can install the aur package gtk3-git that contains the fix. It worked fine for me.
Offline