- From: Johannes Odland via GitHub <noreply@w3.org>
- Date: Fri, 01 Aug 2025 11:38:07 +0000
- To: public-css-archive@w3.org
johannesodland has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-typed-om] Should `serialize a CSSUnparsedValue` append `/**/` between USVStrings? == Step 2.1. of [`serialize a CSSUnparsedValue`](https://drafts.css-houdini.org/css-typed-om/#serialize-a-cssunparsedvalue) appends USVStrings without any separation. > 1. Let s initially be the empty [string](https://infra.spec.whatwg.org/#string). > 2. [For each](https://infra.spec.whatwg.org/#list-iterate) item in this’s [[[tokens]]](https://drafts.css-houdini.org/css-typed-om/#dom-cssunparsedvalue-tokens-slot) internal slot: > 1. If item is a [USVString](https://webidl.spec.whatwg.org/#idl-USVString), append it to s. > 2. Otherwise, item is a [CSSVariableReferenceValue](https://drafts.css-houdini.org/css-typed-om/#cssvariablereferencevalue). Serialize it, then append the result to s. > 3. Return s. Implementations differ here. - Blink append `/**/` between subsequent USVStrings - WebKit does not append anything between subsequent USVStrings - [WPT](https://github.com/web-platform-tests/wpt/blob/20f122c6539d163ff1a150454b0cd497b603b328/css/css-typed-om/stylevalue-serialization/cssUnparsedValue.html#L15) expects `/**/` Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12561 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 August 2025 11:38:08 UTC