this post was submitted on 29 Jun 2025
8 points (90.0% liked)

Firefox

20168 readers
20 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 5 years ago
MODERATORS
 

Firefox seemingly very recently shipped their own titlebar controls buttons, which worsens even further the lackluster OS integration. In the screenshot you see my regular control buttons on the window to the left (default KDE Plasma theme) and the new custom buttons Firefox is serving now.

Would anyone know how to undo that change in about:config or anywhere else?

you are viewing a single comment's thread
view the rest of the comments
[–] that_leaflet@lemmy.world 2 points 12 hours ago (4 children)

Are you using an icon theme? Papirus?

[–] ISOmorph@feddit.org 2 points 11 hours ago (3 children)

Yup, does that break something in the newest update?

[–] that_leaflet@lemmy.world 5 points 11 hours ago (2 children)

Firefox is taking that icon from your GTK theme. And that’s the maximize button in the Papirus theme. So this is intended behavior.

You’d have to modify the theme or tell Firefox to use a title bar to fix it.

[–] Valso@lemmy.ml 1 points 9 hours ago* (last edited 9 hours ago)

If Firefox is using GTK (GTK3 to be precise) to decorate the window, even in KDE, that might be some good news for him, altough I could be wrong bc I've never used Plasma for this long (30 days tops, long ago) to get to the point of wanting to change the title bar of anything. In Cinnamon (6.4.7) I'm using an old workaround for cases like this. It's still somewhat maintained. I can't guarantee it will work with Plasma but it doesn't hurt to try: https://aur.archlinux.org/packages/gtk3-nocsd-git After installation, open (or create) ~/.XSession and put these two lines in it: export GTK_CSD=0 export LD_PRELOAD=/usr/lib/libgtk3-nocsd.so.0 and reboot.

This is how I've been replacing GEdit's CSD with a normal title bar, as well as Firefox's:

load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)