- From: Tom Golden via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Mar 2022 00:16:33 +0000
- To: public-css-archive@w3.org
tbjgolden has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-mediaqueries-4] should color-gamut be evaluated in a boolean context? == At https://www.w3.org/TR/mediaqueries-4/#mq-boolean-context the spec says > media features [...] can also be written more simply as just the feature name, like `(color)`. > > When written like this, the [media feature](https://www.w3.org/TR/mediaqueries-4/#media-feature) is evaluated in a boolean context. > > If the feature would be true for any value other than the number 0, a [<dimension>](https://www.w3.org/TR/css-values-3/#typedef-dimension) with the value 0, or the keyword [none](https://www.w3.org/TR/mediaqueries-4/#valdef-media-update-none), the media feature evaluates to true. If this is the case, then why does it say (in https://www.w3.org/TR/mediaqueries-4/#color-gamut): > Note: Some output devices, such as monochrome displays, cannot support even the [srgb](https://www.w3.org/TR/mediaqueries-4/#valdef-media-color-gamut-srgb) gamut. To test for these devices, you can use this feature in a negated boolean-context fashion: `not (color-gamut)`. --- This means that either: These two sections contradict each other - which one is true? If it's the `not (color-gamut)` should the boolean context section be changed? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7121 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 March 2022 00:16:35 UTC