[csswg-drafts] [css-values-4] Clarify property value ranges (#9133)

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

== [css-values-4] Clarify property value ranges ==
Some parts of the definition of [property value ranges](https://drafts.csswg.org/css-values-4/#component-types) (eg. `<'color'>`) seem confusing to me.

---

  > Property value ranges, which represent the same pattern of values as a property bearing the same name. [...] 
  >
  > These types do not include CSS-wide keywords such as `inherit` [...]

CSS-wide keywords are only included in the value definition of a few properties defined in CSS 2 that are not superseded in a later spec.

I suggest this explicit definition:

  > A type representing a property value range includes the set of values corresponding to its value definition. It does not include global CSS keywords or property substitution values.

At least, property substitution values should also be excluded.

---

  > These types do not include [...] any **top-level comma-separated-list multiplier** (i.e. if a property named pairing is defined as `[ <custom-ident> <integer>? ]#`, then `<'pairing'>` is equivalent to `[ <custom-ident> <integer>? ]`, not `[ <custom-ident> <integer>? ]#`).

If I am not mistaken, this rule targets `#` in value definitions of coordinating list-valued properties. It targets the repetition of *a value that can be declared **alone** for a property*.

For example, to declare `property` defined with `<foo> | <bar>`, `<number>` in `<foo>` can be repeated but not in `<bar>`:

```
<foo> = a <number>#
<bar> = <number>#
```

If I am not mistaken in the example above, this type of grammar definition should obviously be avoided, and I suggest to define this rule with an explicit connection to the concept of *coordinating list property group*.

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


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

Received on Tuesday, 1 August 2023 07:20:34 UTC