![](/static/790fef6/assets/icons/icon-96x96.png)
![](https://lemm.ee/api/v3/image_proxy?url=https%3A%2F%2Flemmy.ml%2Fpictrs%2Fimage%2Fq98XK4sKtw.png)
You’re most certainly welcome.
I wanted to add on this, for anyone else stumbling across this post and struggling with sidebar theming: The above will work 90% of the time, but in case your some-random-theme.css
overrides @sidebar_
, or doesn’t follow the naming convention to begin with, search your gtk.css for .sidebar-pane
, which should be the actual css selector for @sidebar_
, and .content-pane
for @secondary-sidebar_
.
Nah, unless you’re unhappy with the current outcome, you can leave it as it is.
Changes in
.config/gtk-4.0/gtk.css
will be applied on top of the stylesheet, so whatever you don’t override there, will fall back to the default, that’s why your sidebar previously went full Adwaita light mode.After taking a brief look at the libadwaita source, as far as I can see, helper colors are a special case anyways,
@borders
as well asborder_color
is used exclusively in thescss
files (which the gtk.css is generated from), whereas the gtk.css for some reason doesn’t get back to the generic name, but uses the assigned valuealpha(currentColor,0.15)
- which doesn’t help your case at all.To actually change @borders, you would need to modify its value in .scss and regenerate the .css then.
For your other point, there’s no need to introduce a new color for this, since the helper color is an alpha value derived from your foreground color (that’s what currentColor is referring to), so if you change
_fg_color
in gtk.css,@borders
will change along with it.