Roma Komarov

As usual, credits:

- @bramus for his article about `light-dark()`.
- @anniegreens for her post about what she learned about `color-scheme`.
- @argyleink for his recent post about adaptive light/dark color schemes.
- @pepelsbey for the mention of one important difference between `prefers-color-scheme` and `color-scheme` in the latest @webstandards_ru podcast episode.
- @tabatkins for the `<meta name=color-scheme>` CSSWG issue.

Like 29 August at 13:27 | Open on front-end.social

3 comments

Roma Komarov

And, again, as usual, while doing the experiments for this post, I encountered at least two bugs in the browsers:

- An older, now fixed, Chromium bug: https://issues.chromium.org/issues/335383222
- A more recent Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1914735

It is like I encounter bugs almost every time I play with anything, haha.

29 August at 13:30 | Open on front-end.social

Thomas Steiner :chrome:

@kizu When I researched this area for https://web.dev/articles/color-scheme, there were many problems with system colors not getting updated when the mode changed like `Canvas` or `CanvasText`, the default visited link color in dark mode was horribly non-contrasting, and embedded iframes were unusable in dark mode. I'm pretty sure some of these issues are still not fixed in all browsers.

29 August at 19:36 | Open on toot.cafe

Roma Komarov

@tomayac Yeah, I remember that the system colors were very uneven in how they worked, and how the link color was basically broken in the dark mode of Safari at least. I, myself, rarely use these, but at least the `Canvas` and `CanvasText` seem relatively stable today. Although given the UA is free to choose their color, I'd also not rely on them in 100% of cases, but for simple prototypes/simple pages could be fine.

29 August at 19:53 | Open on front-end.social