- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 May 2025 00:32:33 +0000
- To: public-css-archive@w3.org
Hm, that is true, `ident()` is specified to only return a `<custom-ident>`, so I suppose there's no ambiguity. Weird that it requires us to detect a troublesome custom ident and serialize it back out with an `ident()` wrapper, tho, especially since "troublesome" varies by usage site. I suspect we'd screw that up and end up generating serializations that don't round-trip. Stepping back, tho, your example is *already* not parseable at parse time due to the use of `var()`; the `ident()` has nothing to do with this. A simple `scroll-timeline-name: var(--foo)` already troublesome. Are there any cases where we can trigger this "can't determine at parse time" that don't rely on an arbitrary-substitution function? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12206#issuecomment-2902944635 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 May 2025 00:32:34 UTC