Really a big fan of the underlying theme (no pun intended) here which is that your website or webapp <i>should</i> care significantly more about visually fitting in with the user's system, settings, and preferences than it should about expressing your corporate branding and looking the same on every device in the world. Users don't care about your "brand colors" and every "unique" UI element only serves to make their task of learning your site more annoying.<p>In my career I have rarely run across anyone trusted to make visual design calls who is humble enough to agree with the above. Two different shades of black depending on which browser the user chooses? "Quick, file a bug!"
Looks like support for "system colors" is up to 96% in 2023:<p><a href="https://caniuse.com/mdn-css_types_color_system-color" rel="nofollow">https://caniuse.com/mdn-css_types_color_system-color</a>
The CSS spec is always interesting for how much very useful stuff there is in it that’s buried under a magic incantation. I mean that as in, there’s little in the syntax to hint at the fact that Canvas as a colour exists.<p>Some colours are camelCase (currentColor), others are uncased (rebeccapurple) and I guess these system colours are TitleCase? (CanvasText)<p>I guess you just need to know!
I’m mid 30s and have been writing front end code since the late 90s and it never ceases to amaze me how straightforward and easy it has become. When XMLHttpRequest came out it felt like a HUGE hack to load stuff that wasn’t xml. In fact the only way to have a half decent website was to use an arsenal of hacks because browsers sucked
I’ll look at the stylesheet later, but how are they avoiding links on iOS being dark blue on a dark background?<p>iOS’s default “dark” stylesheet is, unfortunately, not usable, and I’ve wondered if there’s a workaround that doesn’t involve me hard-coding specific colors.<p>Edit: relevant WebKit bug: <a href="https://bugs.webkit.org/show_bug.cgi?id=209851" rel="nofollow">https://bugs.webkit.org/show_bug.cgi?id=209851</a>