- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jul 2020 09:56:32 +0000
- To: public-css-archive@w3.org
As @cookiecrook noted in a https://github.com/w3c/csswg-drafts/issues/3856#issuecomment-655806870 or https://github.com/w3c/csswg-drafts/issues/3856#issuecomment-662030770, the scope of this issue is overflowing into a related but distinct topic. The question asked by @fantasai initially has been resolved on, and I've made the edits, so I am closing this issue.
For discussion of whether the `high` value of `prefers-contrast` is appropriate for what macOS does or whether we need a separate one, see #2943
Some comments have also suggested that maybe `@media (prefers-contrast) {...}` should evaluate to true even when none of the existing values (`low`, `high`, and now `forced`) evaluate to true. Either this is because we'd add `increased` and remove `low` (and now `forced`), in which case this fits into #2943, or this goes against the definition of [Evaluating Media Features in a Boolean Context](https://drafts.csswg.org/mediaqueries-5/#mq-boolean-context), and should be raised separately.
If, as a result of these discussions, we end up changing how this media feature works, we may end up deciding to reopen this issue. But it seems to me that quite a few points that @cookiecrook makes here assume that #2943 will be resolved in the direction he proposes, while the resolution that was recorded here assumes currently specified behavior.
This is not an attempt to stifle discussion, but to consolidate each topic in their respective issue, and hopefully make the discussion easier to follow.
--
GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3856#issuecomment-663462475 using your GitHub account
Received on Friday, 24 July 2020 09:56:33 UTC