#Change theme based on UA preference
1 messages · Page 1 of 1 (latest)
While I support this, I would like to see a setting to disable such behaviour if it is added. I use Chromium's Force Dark mode with Bunny's light theme, which works better for my eyes and personal preference, forcing dark on dark would look worse, and (no offence to the FE Bunnies) I don't like Bunny's own dark theme, an opinion I share about many other site's dark themes, such as the one in AdGuard Home.
I don't mind the dark mode
I get that but my point is if Bunny were to auto switch it to dark mode without my involvement it would be dark on dark, Chromium doesn't care if the site is already dark or not, in fact, it can't tell 🤣
I mean, don't even get me started 😓
On desktop, some sites break entirely with force dark (like bgp.tools), rendering them unusable without injecting some CSS to trick the rendering engine. On mobile, I am lucky that Cromite has re-added the old dark mode toggle, however on PC, issues like that are unavoidable, it's either on or off, so in addition to that issue, if Bunny were to do this, I would have to inject CSS to fix it, and guess what that CSS would do...? It makes Dark Mode fully disable itself, so it's only a last last last resort, so then I'd be back to square one with NO dark mode.
Dark Reader might not do the best job at times but it at least disables itself on dark mode websites so it doesn't break styles which is why I use it
Yeah, but my threat model means I can only run limited numbers of extensions, Dark Reader is FP-able. Can't use it.
If you inject CSS or JS into a page, it can be FP'd. Try CreepJS's test page, it can detect it.
Meanwhile with Cromite, CreepJS stands no chance. It can't FP it at all.
Keep dark reader on and take note of the fuzzy and diffs, then turn it off and compare the results.
https://abrahamjuliot.github.io/creepjs
I cannot recall for sure, but, I believe you may also get even more of a different result if you hard-disable it in extension options as well. From the brief tests I did a long while back, even with it off in the dark reader menu, it leaves some artifacts behind, again, don't quote me on that.
Meanwhile Chromium's #force-dark flag uses the rendering engine, fully client side, so there is no way for a site to detect it, as far as I know it's similar to just putting a literal filter on your display's output, even the CSS remains untouched.
It does this
It leaves marks in <html>
I can check for dark reader by checking for attributes in <html>
A lot of my sites break because of dark reader so I could probably just add an overlay using CSS based on attributes
To fix issues with sites, I use the same trick that I use on my main website to try to hint to extensions, etc, that my site is light mode only (this is because my site is retro themed, and looks stupid in dark mode)
I inject <meta name="color-scheme" content="only light"> into <head> using my userscript manager, with it set to execute the script before load.
to avoid fingerprinting, i use match rules in the userscript header 😉
for example; Match: https://bgp.tools/*
I have raised this issue with Ben though, and he said he'd consider adding the meta snippet himself as a fix.