[csswg-drafts] [css-values-4] Serialization of Functional Notations (#9720)

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

== [css-values-4] Serialization of Functional Notations ==
Tab and I noticed that we don't rigorously define the serialization of functional notations, so we're proposing to add a generic definition to CSS Values L4.

The non-controversial aspects are:

- Serialize the arguments per their individual grammars.
- Commas serialize with a following space.
- Space-separate adjacent tokens (except between a value and a following comma)

The one area where we have very little agreement is

- Whether to omit optional values in specified value serialization.

Generally-speaking, we omit optional components in computed values. This is an important principle of CSSOM serialization for computed values. But we are very inconsistent for specified values--this is extra confused by the fact that multiple "serialization" sections in our specs don't distinguish between specified and computed values and just assume there's only one serialization.

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


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

Received on Monday, 18 December 2023 20:34:53 UTC