- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Feb 2025 04:04:56 +0000
- To: public-css-archive@w3.org
nt1m has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-values] Distinction between `attr(foo type(<string>))` and `attr(foo string)` is too subtle == One parses the string and strips whitespace, the other reflects the string as-is. As an author, it's hard to know what the difference it without reading documentation. Possible ways to accommodate this: * remove the `string` keyword entirely, make the `attr(foo)` the _only_ way to express this * find another keyword that makes the difference more explicit `unparsed-string` or `as-string` ? cc @tursunova @tabatkins @fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11645 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 February 2025 04:04:57 UTC