Dark mode is here for Wikipedia (finally!). Dark mode has been one of the most requested features. It improves accessibility and reduces eye strain for readers and communities across Wikimedia proj…
So, if I’m reading this right it’s basically just a 17 paragraph essay that boils down to, “Sorry we suck at CSS and it took us a decade to finally get around to rooting out all the random shit from 2014 that was hard-coded to display as rgb(0,0,0) or whatever, which was a capability that in retrospect we really shouldn’t have handed out like candy?”
The TV Tropes wiki has managed to have a built in dark mode for at least the last 7 years. TV Tropes. Come on, guys.
I’m baffled by the section about “making a shortcut that darkens all the colors on the page.” I’m positive that’s the intent of that entire blurb, to dazzle people with bullshit in the hopes that they won’t ask Hard Questions, because no competent designer would ever try such a thing. It is a self-evidently moronic idea. You don’t fuck with elements you didn’t create and don’t control, like images and color swatches.
There are only really two viable possibilities, here:
If arbitrary user definable, hard-coded colors in content are permissible, you’ll have to accept the fact that the cards will fall where they may and some instances will inherently be suboptimal in either light or dark modes, or…
Accept that you won’t allow users to hard-code colors into anything outside of specific elements where that usage is valid, so users will just have to suck it up and pick from a list of preapproved color combinations with light and dark mode renditions.
The TV Tropes wiki has managed to have a built in dark mode for at least the last 7 years. TV Tropes. Come on, guys.
It’d be kind of interesting to have a “dark mode spider” that crawls the Web and checks to see what percentage of websites support the browser-requested dark mode. I’d be kind of curious to see how far along we are.
I mean, people have done it for stuff like IPv6 support for a while.
Oh, it’s a tool that you run on one page, rather than a spider to try to gather statistics on the Web as a whole. But, yeah, that run en masse could maybe gather that kind of information.
Websites specifying color for foreground (or background) and assuming browsers will use whatever color they’re expecting for the other has always existed, and still exists
If you’re getting fancy and specifying colors, you can’t cheap out and not specify all colors
If the browser ignores all your colors at that point, then it’s displaying as the user intended
If you only specified some of the colors, it’s a bug of the website
There are actually things websites can do which may be more common than you’d think. At a high level you could convert all the custom colours to HSV format and slightly lower the value and saturation according to some function. This is fairly common for images.
So, if I’m reading this right it’s basically just a 17 paragraph essay that boils down to, “Sorry we suck at CSS and it took us a decade to finally get around to rooting out all the random shit from 2014 that was hard-coded to display as rgb(0,0,0) or whatever, which was a capability that in retrospect we really shouldn’t have handed out like candy?”
The TV Tropes wiki has managed to have a built in dark mode for at least the last 7 years. TV Tropes. Come on, guys.
I’m baffled by the section about “making a shortcut that darkens all the colors on the page.” I’m positive that’s the intent of that entire blurb, to dazzle people with bullshit in the hopes that they won’t ask Hard Questions, because no competent designer would ever try such a thing. It is a self-evidently moronic idea. You don’t fuck with elements you didn’t create and don’t control, like images and color swatches.
There are only really two viable possibilities, here:
It’d be kind of interesting to have a “dark mode spider” that crawls the Web and checks to see what percentage of websites support the browser-requested dark mode. I’d be kind of curious to see how far along we are.
I mean, people have done it for stuff like IPv6 support for a while.
Didn’t Google’s lighthouse have a metric for that? “Colour Contrast ratio” or something?
Not familiar with it.
goes looking
Oh, it’s a tool that you run on one page, rather than a spider to try to gather statistics on the Web as a whole. But, yeah, that run en masse could maybe gather that kind of information.
Isn’t #2 the only option?
Websites specifying color for foreground (or background) and assuming browsers will use whatever color they’re expecting for the other has always existed, and still exists
If you’re getting fancy and specifying colors, you can’t cheap out and not specify all colors
If the browser ignores all your colors at that point, then it’s displaying as the user intended
If you only specified some of the colors, it’s a bug of the website
There are actually things websites can do which may be more common than you’d think. At a high level you could convert all the custom colours to HSV format and slightly lower the value and saturation according to some function. This is fairly common for images.
Like how amazing an innovation in NYC the technology which is… Plastic trash cans! With lids!