3 ms·
with dark-reader you still have the problem of getting blinded at night for the first second or so until the DOM finished parsing. There were some workarounds w
by DyslexicAtheist 6y ago
with dark-reader you still have the problem of getting blinded at night for the first second or so until the DOM finished parsing. There were some workarounds with userChrome.css userContent.css that solved this for a while, but they broke in recent builds so I'm back to feeling like a deer staring at the headlights every time a new tab opens on a page.
I'm not 100% certain that this should be forced by the browser and IMHO it's the websites owners job to provide properly working dark theme and the UI/UE they think fits best their purpose (and not the browsers). Unless the assumption is that styling across all sites should look 100% identical which may appeal to some, though if I really want that then I can go look for content on gemini:// and no page will ever use their own styling other than what I am telling it to. Maybe it's just me but I like being dazzled and surprised with new design and style that I've not seen before.
- GoblinSlayer 6y agoIf rendering was server's concern, you would be served jpegs, not html.
- jrockway 6y agoYou're definitely right about being blinded during a startup delay. It's not every site but it does happen. I agree that all websites should give users a dark mode. They don't, so we have to make our own.