- From: Jonathan Kingston via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Nov 2018 23:30:27 +0000
- To: public-css-archive@w3.org
> I (but note I'm not an expert in this area) personally think no-preference should be exclusive to any of the other values matching (that is, you should never get into a state where (prefers-color-scheme: {light, dark}) and (prefers-color-scheme: no-preference) apply at the same time. Also, it probably makes sense to require at least one of the values to match over all?
That seems to be my understanding of how this should work also. I think it is fair that Safari for example might decide never to match for `no-preference` as they are always `light` or `dark`.
As for Firefox, for the short term `no-preference` might be used on platforms where we don't have an OS setting. Firefox likely will be using `no-preference` for users who don't want to convey their preference also like Tor users.
My views are:
- `no-preference` should never match when `light` or `dark` does.
- `(prefers-color-scheme)` should match if `light` or `dark` matches but not match when `no-preference` matches.
--
GitHub Notification of comment by jonathanKingston
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3278#issuecomment-438858192 using your GitHub account
Received on Wednesday, 14 November 2018 23:30:28 UTC