- From: Sam Atkins via GitHub <noreply@w3.org>
- Date: Tue, 17 Jun 2025 13:52:33 +0000
- To: public-css-archive@w3.org
AtkinsSJ has just created a new issue for https://github.com/w3c/csswg-drafts: == Inconsistency between `@property { syntax }` (quoted) and `attr(type())` (unquoted) == At least on a surface level, these are very similar: a description of the syntax to use when parsing some arbitrary CSS tokens. The only difference I can spot between the two definitions ([1](https://drafts.csswg.org/css-values-5/#typedef-syntax), [2](https://drafts.css-houdini.org/css-properties-values-api-1/#syntax-strings)) is that `syntax` can take a single `*`. However, `syntax` takes this grammar wrapped in a `<string>`, and `type()` takes it unquoted, using a new `<syntax>` type. Is there a reason why `type()` can't also take a string, or has it just been overlooked? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12353 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 June 2025 13:52:34 UTC