You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
Recently, I updated to GNOME 45, and started noticing oddities with the dark mode (figure 1)
I decided to ask for help in how to enable the dark mode, where I learned that I had leftover CSS from Gradience, which I had not used in months (and had not noticed the difference in GNOME 44 from stock).
The warning in app currently describes theming related issues (figure 2), but has no mention towards the permanence of these changes after the app ceases to exist.
Proposal
Edit the warning to inform the user that CSS can remain after removal of Gradience.
Additional
Instead of directly writing the CSS file under ~/.config/gtk-4.0/gtk.css, write under an internal app directory and create a symbolic link under ~/.config/gtk-4.0/. This can utilize the new GNOME 45 capability of prompting the user to delete app data after removal of a flatpak.
Feature description
Background
Recently, I updated to GNOME 45, and started noticing oddities with the dark mode (figure 1)
I decided to ask for help in how to enable the dark mode, where I learned that I had leftover CSS from Gradience, which I had not used in months (and had not noticed the difference in GNOME 44 from stock).
The warning in app currently describes theming related issues (figure 2), but has no mention towards the permanence of these changes after the app ceases to exist.
Proposal
Edit the warning to inform the user that CSS can remain after removal of Gradience.
Additional
Instead of directly writing the CSS file under
~/.config/gtk-4.0/gtk.css
, write under an internal app directory and create a symbolic link under~/.config/gtk-4.0/
. This can utilize the new GNOME 45 capability of prompting the user to delete app data after removal of a flatpak.Additional Context
Figure 1
Figure 2
Did you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: