[css-values-5] Does `container-progress()` really want the entire `<size-feature>` production for its progress value?

[cdoublev]

Similarly as requested in #10966, container-progress() should probably take a <mf-name> corresponding to a size feature, instead of a whole <size-feature>, which is the same as for a media feature: a feature name, a comparator, and a value (emphasize added on what is unexpected).

Perhaps you would like to use something like <size-feature-name> to avoid the confusion with media features.

[fantasai]

Fixed the error, tagging against relevant specs to give these things proper productions.

[cdoublev]

Thank you. Related to "give these things proper productions": #10790. Basically, this proposal would now be <condition[ <feature-name> ]>. But I am not sure this would be an appropriate use of the new <type[ <subtype> ]> concept.

---

The specified <mf-name> must be a valid size feature

This does not explicitly require a "range" size feature, like for the media feature in media-progress(). However I am not sure if this is necessary because container-progress(orientation, 1px, 1px) would still be invalid since 1px is an invalid value for orientation. I think grid is the only feature that accepts numeric values but is not a range feature.