- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 May 2023 06:31:36 +0000
- To: public-css-archive@w3.org
I'm sceptical about switching tokenizer modes as a _general_ concept that can happen anywhere, because tokenization is logically separated from parsing (in Blink anyway), and in many cases we tokenize the input in full before looking at any of the tokens (which means it's too late to switch modes by the time we discover the need for that switch). I think the current spec is not too unreasonble, except for the requirement that tokens retain their representation. Thought: implementations must already be able to retain the original string for _declarations_ due to custom properties, can we work with that here? - Remove `<urange>`, instead: - `unicode-range: <any-value>`. - Spec that `unicode-range` retains the original string of its declaration, exactly like custom props. - At some point interpret that original string into a range per [7.1](https://www.w3.org/TR/css-syntax-3/#urange-syntax). --- How would we define `unicode-range` if we introduced it today? `unicode-range: <string>`? -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8835#issuecomment-1552528306 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 May 2023 06:31:37 UTC