The dark mode is actually coming from the GNOME system colors, not browser plugin.
From inspecting the CSS in the developer console, the cases in the screenshot either set the background color without setting the text color, or vice versa.
From inspecting the CSS in the developer console, the cases in the screenshot either set the background color without setting the text color, or vice versa.
It's the same when you are using classic Windows theming and change the colors. The default background and font colors adjust accordingly (in Firefox, Chrome and Chromium-based things like Steam), which means that (many) pages that only alter the font color to say #333, but don't change the background color, become completely unreadable. Black on black.
Web developers are just not terribly competent. It should be obvious that setting text color but not text background is erroneous. Since expecting basic competence from web developers seems to be a losing battle several things suggest themselves.
- provide a gui option to select the theme/style to use for firefox separate from the gui. This is already possible at the command line.
- Explicitly check for text that is to close to the background wherein only one attribute is set and adjust the smartest solution
- Just ignore the users colors like chrome does.
Personally I have a dark gtk theme but run firefox with a light one because otherwise the web is unusable.
or whatever your desired theme is
in fact I have the following fish shell function
function withtheme
env GTK_THEME=$argv[1] $argv[2..-1]
end
You can copy the firefox desktop file from /usr/share/applications to ~/.local/share/applications and edit the exec line as you please.