[css-houdini-drafts] [css-typed-om] Serialization for CSSUnparsedValue doesn't match tested behaviour (#1148)

AtkinsSJ has just created a new issue for https://github.com/w3c/css-houdini-drafts:

== [css-typed-om] Serialization for CSSUnparsedValue doesn't match tested behaviour ==
A couple of issues here:

---

[serialize a CSSVariableReferenceValue](https://drafts.css-houdini.org/css-typed-om-1/#serialize-a-cssvariablereferencevalue) step 3 says:

> 3. If this’s [fallback](https://drafts.css-houdini.org/css-typed-om-1/#dom-cssvariablereferencevalue-fallback) internal slot is not null, append ", " to s, then serialize the [fallback](https://drafts.css-houdini.org/css-typed-om-1/#dom-cssvariablereferencevalue-fallback) internal slot and append it to s.

However, the tested behaviour in https://wpt.live/css/css-typed-om/stylevalue-serialization/cssUnparsedValue.html requires that "," without a space is appended instead.

---

[serialize a CSSUnparsedValue](https://drafts.css-houdini.org/css-typed-om-1/#serialize-a-cssunparsedvalue) somehow needs to obey the comment-insertion rules as described [here](https://drafts.csswg.org/css-syntax/#serialization). This is awkward because we have a list of strings and CSSVariableReferenceValues, not CSS tokens.

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


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

Received on Thursday, 14 August 2025 15:37:26 UTC