I thought this was going to be about how people prefer different levels of blackness for the background in dark mode. I've heard people say that pure black is more battery efficient for OLED displays (but don't know if this is true), and I know some folks prefer a less-inky grey.
I was wondering how there could be six levels though; I'd think 3 or 4 would be the most anyone could notice or care about.
>I've heard people say that pure black is more battery efficient for OLED displays (but don't know if this is true)
No.
https://www.xda-developers.com/amoled-black-vs-gray-dark-mod...
The more universal solution would be to standardize Reader Mode compatibility, and for browsers to let users configure how they want Reader Mode to look.
In other words, instead of an n x m solution where every web site has to cater to each different user preference, there should be a simplified content view that every web site only has to support in a singular way, and that allows browsers to cater to the various user preferences.
This likely would have happened already if it weren't for Google's hostility to Reader Mode. It's hilarious to see the Reader Mode that they offer, where it's a resizable 2-column view, to ensure that ads are loaded and kept in sight. We get it, Google: you don't want to endanger your ad revenue.
It's just n x 2 for light and dark themes.
Grayish dark themes are underrated
for OLEDs, I tend to prefer pure black because it doesn't burn-in. Since they have a limited lifetime, any "on" time is costing me usage in the long-long-long run and I'd rather have my monitor last 5+ years than ... 2 or 3.
>any "on" time is costing me usage in the long-long-long run and I'd rather have my monitor last 5+ years than ... 2 or 3.
Going from dark gray to pure black isn't going to halve your monitor expectancy, if it makes a difference at all. Due to how human perception works something that's merely dark gray is actually orders of magnitude brighter than pure white, or even 50% gray. Therefore most of your burn-in is going to be driven by bright content like photos or white text, not whether you're using 5% gray vs pure black.
> Dedicated files make sense if you do a lot of customization. The browser may ignore any CSS file that does not match the query, so there’ll be one less thing to download.
That’s not how it actually works: in practice, browsers download them all. They may prioritise them differently, but they’ll still download them all in the end.
Is there still no way to prevent the flash bang while waiting for initial content from the server?
I don't know if I misunderstand the problem, but what about a style tag at the earliest part of the page indicating the background color to use?
That flashbang happens during the initial latency (DNS, RTT, any server slowness).
Use `background-color` in Firefox's `userContent.css`.
I love the idea of ending it for myself, but my users are still screwed?
send a blank black page then load from there?
make dark mode the default, then it's a flash of dark in either case
Decrease screen brightness. Turn off dark mode. No flashbang. Bonus: Battery lasts longer.
Glad OP got the tri-state toggle right!
Level 9 (or 0): Turn off the computer and go to sleep.
Would've been cool if the levels came into effect while you scrolled down the page
Or were selectable by the reader at each appropriate position in the page.
It's 8 levels though?
Obligatory ? https://xkcd.com/3227/
so sad that he disabled this ability to propagate to other pages :(
it was the first time my eyes got comfortable reading his comics
Ah, the unofficial sequel to The Last Question.
2024