So, CSS variable support has landed in GTK, and libadwaita now uses it. Note that it's super basic for now, it's just replacements for the old `@colors`. There will be more drastic changes in 2.0, but for now I need to keep backwards compatibility.
So, apps can now override them per widget, like on the screenshot (well, once the sdk updates, anyway)
And because why not, there are a few changes that variables enabled:
`.error`, `.warning` and `.success` style classes now also change the accent color respectively. For example, this means that a selectable label with .error style class will have a red selection as well, instead of blue.
The `.opaque` style class for buttons has been deprecated - instead, apps can simply use `.suggested-action` and override the accent color on it (or add `.error`/`.warning`/`.success` - that works too). This will also change the focus ring, and similarly, `.destructive-action` buttons have red focus rings now.
Apps are encouraged to migrate, but the old colors will keep working until 2.0. For example, `@accent_color` can be replaced with `var(--accent-color)` and so on, note the dashes in the names instead of underscores. See the docs for more info: https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/css-variables.html
https://mk.nyaa.place/files/3f9056d3-6728-4e51-9cb4-b241fa771782
Alice :neocat_flag_transbian: /
npub1xd…fdv8q
2024-05-13 19:32:08
Author Public Key
npub1xdcfc9y32lgtv3ln76lgmd5vt0t8tejpe4q02h8zl6dpu9khwpds4fdv8qPublished at
2024-05-13 19:32:08Event JSON
{
"id": "3bf47e5019be283443c6979dc5f8f026f68ce6a6f2d598aa26f41f1498a33f00",
"pubkey": "33709c149157d0b647f3f6be8db68c5bd675e641cd40f55ce2fe9a1e16d7705b",
"created_at": 1715628728,
"kind": 1,
"tags": [
[
"imeta",
"url https://mk.nyaa.place/files/3f9056d3-6728-4e51-9cb4-b241fa771782",
"m image/webp"
],
[
"proxy",
"https://mk.nyaa.place/notes/9t8xd0oi6lio09xv",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mk.nyaa.place/notes/9t8xd0oi6lio09xv",
"pink.momostr"
]
],
"content": "So, CSS variable support has landed in GTK, and libadwaita now uses it. Note that it's super basic for now, it's just replacements for the old `@colors`. There will be more drastic changes in 2.0, but for now I need to keep backwards compatibility.\n\nSo, apps can now override them per widget, like on the screenshot (well, once the sdk updates, anyway)\n\nAnd because why not, there are a few changes that variables enabled:\n\n`.error`, `.warning` and `.success` style classes now also change the accent color respectively. For example, this means that a selectable label with .error style class will have a red selection as well, instead of blue.\n\nThe `.opaque` style class for buttons has been deprecated - instead, apps can simply use `.suggested-action` and override the accent color on it (or add `.error`/`.warning`/`.success` - that works too). This will also change the focus ring, and similarly, `.destructive-action` buttons have red focus rings now.\n\nApps are encouraged to migrate, but the old colors will keep working until 2.0. For example, `@accent_color` can be replaced with `var(--accent-color)` and so on, note the dashes in the names instead of underscores. See the docs for more info: https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/css-variables.html\nhttps://mk.nyaa.place/files/3f9056d3-6728-4e51-9cb4-b241fa771782\n",
"sig": "c3326445346f89f2aa44409cf35195472cd5633b0b37405ed5896eb252c36fb21907033796759177f40a9994e1a67e02fde884f571d1c2acacdb6084f49e3dcd"
}