- From: Kevin Babbitt via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 May 2025 18:39:42 +0000
- To: public-css-archive@w3.org
7164 led to [Appendix A: Coordinating List-Valued Properties](https://www.w3.org/TR/css-values-4/#linked-properties), but I don't think that section is applicable in this case. Unlike backgrounds, transitions, or animations, there isn't a single "coordinating property" here: width, style, and color are all on equal footing, so to speak. We could define one of those as the coordinating property, but it's not clear to me that it would make things any simpler in this case. The sticking point I see is auto repeaters, because we don't know at computed-value time how many expansions will be generated. I would look to CSSOM's [Serializing CSS Values](https://www.w3.org/TR/cssom/#serializing-css-values): > 1. Let *shorthand* be the first shorthand property, in [preferred order](https://www.w3.org/TR/cssom/#concept-shorthands-preferred-order), that exactly maps to all of the longhand properties in *list*. > 2. If there is no such shorthand or *shorthand* cannot exactly represent the values of all the properties in *list*, return the empty string. > 3. Otherwise, [serialize a CSS value](https://www.w3.org/TR/cssom/#serialize-a-css-value) from a hypothetical declaration of the property *shorthand* with its value representing the combined values of the declarations in *list*. If the repeaters happen to line up across the three properties, it's pretty trivial to construct an equivalent shorthand. If the repeaters don't line up exactly, it *may* still be possible to construct an equivalent shorthand by expanding integer repeaters. (The same should hold for specified values, btw.) -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12201#issuecomment-2895456111 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 May 2025 18:39:43 UTC