- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 May 2019 20:15:35 +0000
- To: public-css-archive@w3.org
Summarizing from David's point in the minutes: We don't necessarily need the 'color-scheme' property and (prefers-color-scheme) MQs to be in perfect alignment. In particular, we can define that "color-scheme: light" (or dark) just means that the UA's colors will generally be dark-fg-light-bg. That categorization matches the UA default, a high-contrast black-on-white, or even sepia (which is sepia-fg-white-bg). This would mean that pages generically opt themselves into *some kind of* light (or dark) color scheme, without knowing the details beyond the aforementioned broad strokes about fg/bg lightness. Then the MQ can provide more detailed information for authors to specifically respond to if they'd like; `(prefers-color-scheme: sepia)` makes a lot of sense to add and respond to. We'll have to put a little bit of thought into the MQ categories then, since presumably "light" and "dark" would still be supercategories there, so if we're carving out "sepia" we might want to also carve out some other common light schemes (like high-contrast white-on-black) ----------- I like this quite a bit, as it handles lots of variation reasonably well. For example, the Nook app on Android has four different "light" themes (black on white, sepia on cream, black on pale brown, and black on light gray), two "dark" themes (white on black, light gray on dark gray), and one that's kinda light but a little weird (dark red on light red, presumably to help reduce blue light during evening reading) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3853#issuecomment-497846175 using your GitHub account
Received on Friday, 31 May 2019 20:15:36 UTC