- From: jfkthame via GitHub <noreply@w3.org>
- Date: Fri, 13 Feb 2026 10:54:38 +0000
- To: public-css-archive@w3.org
> > This highlights an additional case that should be mentioned in the Option 2 rules for when the value must be quoted: if the value contains leading, trailing, or multiple consecutive spaces. > > Doesn't it already cover that? Spaces are not alphanumeric and need escapes so the value serializes as `<string>`. Oh, right: I hadn't thought of spaces as being "non-alphanumeric ASCII", but by a strict interpretation I suppose they are. However, that would mean that even a single space forces `<string>` serialization, in which case the fallback to "otherwise serialize as space-separated idents" is confusing, because there wouldn't ever be multiple idents involved. But I don't think that was the intention: AIUI, the intent is that a multi-word name like `Gill Sans` does _not_ need to be quoted, even though it contains a space. (Nor does its space need to be escaped.) So the suggested rules still need some refinement, I think, in order to clearly capture the intended behavior. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5846#issuecomment-3896536031 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 February 2026 10:54:39 UTC