- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Apr 2019 23:44:19 +0000
- To: public-css-archive@w3.org
@emilio Please, let's not continue to call this “high contrast”. Rossen has already pointed out that it's also used to enforce low contrast, and we need to be clear when discussing it that it is not synonymous with a request for high contrast. Wrt not being able to override... the user could theoretically set `* { forced-colors-adjust: auto !important; }`, which would prevent the page from making any customizations. I don't know too much about the use cases that prompted this property, but my inclination is, if MSFT has found this property to be necessary, we'll probably need to include it. However, I think they did find that usage declined significantly with their current version of the feature, so maybe it's not needed anymore. If they're continuing to ship it, though, I would like us to standardize it. @grorg Dark mode is interesting, and I imagine in some cases it might be a user's base preference and for others they might prefer enforcing it. If inversion (rather than forced colors) is the path you're choosing for enforcement, I imagine you might end up with an option for "let the page do as it likes if it supports the appropriate color mode, otherwise invert". The media queries we have can express this state in case the author wants to query it and make adjustments... except we're not clear on the method of color inversion. If the author needs to invert images, or if it can depend on the UA doing so, or if hues will be distorted or preserved, those are important distinctions we need to be able to make. In other words, the inverted-colors MQ needs to be specific enough that the expected work the author needs to do is very clear and does not need to differ depending on the UA/OS/version, only on MQ values that they can legitimately query! -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3807#issuecomment-482374628 using your GitHub account
Received on Thursday, 11 April 2019 23:44:51 UTC