8000 [css-mediaqueries-4] should color-gamut be evaluated in a boolean context? · Issue #7121 · w3c/csswg-drafts · GitHub
[go: up one dir, main page]

Skip to content

[css-mediaqueries-4] should color-gamut be evaluated in a boolean context? #7121

@tbjgolden

Description

@tbjgolden

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 is evaluated in a boolean context.

If the feature would be true for any value other than the number 0, a with the value 0, or the keyword none, the media feature evaluates to true.

And about color gamut it says (in https://www.w3.org/TR/mediaqueries-4/#color-gamut):

Note: Some output devices, such as monochrome displays, cannot support even the srgb gamut. To test for these devices, you can use this feature in a negated boolean-context fashion: not (color-gamut).

If this is the case, then surely it would be impossible for color-gamut to evaluate as false, as it doesn't support 0 or none


These two sections contradict each other - which one is true? If it's the not (color-gamut) should the boolean context section be changed?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0