[csswg-drafts] [css-values-5] Does media-progress() really want the entire <media-feature> production for its progress value? (#10966)

weinig has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-values-5] Does media-progress() really want the entire <media-feature> production for its progress value? ==
I am trying to wrap my head around the [media-progress()](https://drafts.csswg.org/css-values-5/#media-progress-func) function and am having trouble understanding exactly what kind of `<media-feature>`s should be supported as the progress value.

The stated production, `<media-feature>`, is [defined](https://drafts.csswg.org/mediaqueries-5/#typedef-media-feature) to allow a whole host of syntaxes:

```
<media-feature> = ( [ <mf-plain> | <mf-boolean> | <mf-range> ] )
```

meaning it can match things like `width > 0`, `orientation: portrait`, etc.

The spec does state: "The specified [media query](https://drafts.csswg.org/mediaqueries-5/#media-query) must be a valid “range” type query", but I can't figure out how to map that to a spec concept.

From the tests in WPT, which use only `width` and `height` as features, making me think that perhaps the grammar should be changed to use [`<mf-name>`](https://drafts.csswg.org/mediaqueries-5/#typedef-mf-name) rather than[ `<media-feature>`](https://drafts.csswg.org/mediaqueries-5/#typedef-media-feature).

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10966 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 27 September 2024 16:14:32 UTC