Re: [csswg-drafts] [css-values] A way to dynamically construct custom-ident and dashed-ident values (#9141)

I was originally not in favor of this, but I've been seeing a number of use cases. Even if it's not the optimal solution for all of them, it can serve as a flexible low-level workaround for many, and seems fairly easy to implement.

Syntax-wise, I don't think comma-separated is needed, whitespace-separated is what we do in other places where string concatenation happens (e.g. `content`), and that allows more room for expansion later (unless you think we may want to attach metadata to some of the parts, then comma-separated leaves more room).

Do we need a separate `dashed-ident()` function? It seems an `ident()` would cover that too. What's the additional benefit of `dashed-ident()? It's not even shorter, compare:

```
dashed-ident(var(--foo))
ident("--" var(--foo))
```

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9141#issuecomment-2407792363 using your GitHub account


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

Received on Friday, 11 October 2024 16:53:56 UTC