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
59534 readers
3196 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 1 year 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.
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.