612
Dark mode’s bright future: How dark mode will transform Wikipedia’s accessibility
(diff.wikimedia.org)
this post was submitted on 18 Jul 2024
612 points (98.1% liked)
Technology
59979 readers
2365 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Native dark modes are better and have much less of a performance impact. It’s good as a stop gap though.
Agreed. Well, I don't know if it'd deal with random images as well, as users can upload those.
For a number of sites, you can just get away with running Dark Reader in static mode and it works well enough. Considerably faster.
EDIT: Actually, thanks for reminding me. I've never donated to Dark Reader, and it looks like they ask for a $10 donation if you use it regularly, and that plugin has dramatically improved my Web-browsing experience. Going to do that now.
Also just donated
Dark reader team be like "Guys! We're eating pizza tonight!"
Maybe. Does it make a big performance difference which css (dark reader or delivered by wiki) is used?
Is it known how the default to dark mode setting is persisted if let's say a plugin removed all the Wikipedia cookies on window close? A get or post parameter?
Either way it's a good thing that wiki offers a dark mode.
Dark reader is one of the heaviest extensions you use, lots of dom modifications. It also passes around far too much data between processes.
That's good to know. These modifications are needed to replace the style sheet details, I guess?
What does this mean? Do you have a link where I could read up on the details? Thanks.
Webextensions get their own webprocess as well as running in the website. I don’t have a link but if you read their source they just pass a lot of data to their process to determine things (last i looked some years ago).
There is a trade off of executing more things on the site vs transferring a lot of data. Either way it’s a heavy extension.
"Native". That every webpage has to implement it themselves is sad. Could be a browser feature that overrides some colors on dark.
Then again, with webapps, probably not.
This is sorta how dark reader and such works. It turns out that implementing dark mode for most websites is more complicated than inverting all the css colors. For example, some gray on white text might have enough contrast to be easily read, but when inverted the text is hard to discern or nearly invisible. Images too, they might have a white background but not look good when inverted. Native support is better
Funny enough they do. Before Dark Reader on Firefox on Android I had a Chrome flag that did the same thing. But Dark Reader does a better job IMO.
Chrome flag works on some websites, but makes others completely unreadable. Do not recommend unless you can't use dark reader