- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Jun 2019 00:56:52 +0000
- To: public-css-archive@w3.org
I have to agree with Myles: the terms "light" and "dark" are consistently used in UIs as equal alternatives. Saying that only one of those values is a meaningful choice is user-hostile. Since many websites are by default light, many website authors are going to specifically query for dark preference to serve an alternative design. But as the trendiness of dark mode reaches it peak, and there's more discussion about the [readability benefits of traditional dark text on light backgrounds](https://www.wired.com/story/do-you-need-dark-mode/), I expect that some sites (and maybe even native apps) which were traditionally designed with dark backgrounds will start querying for a light mode preference. I would still prefer _as a user_ to have more nuanced options in my browser: to be able to set no-preference, use a different mode than my OS, or toggle light/dark preferences for individual websites. And I think it's fair for the spec to say that browsers _should_ give users a no-preference (let the website choose) option. But the absence of that option in some environments is not enough justification to specify that browsers must ignore an explicit user choice for "light" mode, treating it as default/no preference. Authors with default-dark styles should be able to detect a light mode preference to trigger alternate designs, just like authors with default-light styles want to be able to detect a dark mode preference. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3857#issuecomment-502903726 using your GitHub account
Received on Tuesday, 18 June 2019 00:56:53 UTC