- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Oct 2020 13:43:20 +0000
- To: public-css-archive@w3.org
Suggesting an alternative approach here.
Maybe general-purpose string concatenation is too low-level for CSS.
Instead, I'm suggesting to treat every string-requiring CSS property differently.
- For paths, allow constructing paths without strings (see here: https://github.com/w3c/csswg-drafts/issues/5674#issuecomment-719067583)
- For urls, allow the `url` function to take more than one argument and have that function concat them.
- For some of the other props requiring strings, like `content`, allow string concatenation in the same way that it's done today, by having several arguments (e.g. `content: "(" attr(title) ")"`, or `font-family: "Times-New-Roman", var(--fallback)`)
The reason for this is a sense that strings inside CSS may create a "language within a language" for each property, (which is already my sense with e.g. `path` strings).
--
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/542#issuecomment-719559989 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 October 2020 13:43:22 UTC