3 ms·
I don't understand the issue? The first screenshot (CSS Theming) shows an app that doesn't use standard background color (?offwhite?), but uses standard font c
by adamzochowski 3y ago
I don't understand the issue?
The first screenshot (CSS Theming) shows an app that doesn't use standard background color (?offwhite?), but uses standard font color. Normally this works, as standard font color is something dark (?black?).
And the problem becomes when user opens the app in dark mode, the background color stays non standard (?offwhite?), but the font color stays standard, which in dark mode makes fonts bright (?white?).
The question is:
If developer is ignoring theming, why don't they hard code both background and foreground colors?
There is one solution : stop using off theme coloring
This is squarely for developer to fix.
But since they want Gnome/GTK to fix this, here are potential options:
- Gnome / GTK should implement that if someone wants to use non standard, off theme colors, then developer has to always define foreground and background color. --- not sure how feasible it this with nested frames
- Gnome / GTK should disable allowing changing colors to specific values, and only allow changing by rotating Hue (aka 5% rotation of Hue 'clockwise') and by changing saturating (aka 5% more grayscale) and by changing brightness/contrast in relation to paired color (aka: background 5% closer shade to font)
- Gnome / GTK should define more color pairs , kind of like bootstrap has primary/secondary/success/danger/warning/info/light/dark coloring for all components in a single theme