Re: [csswg-drafts] [css-syntax] custom property names too permissive, require namespacing rules (#7129)

Programming languages such as JS and Java that allow non-ASCII variable names with character limits usually have different restrictions for the initial character. Most notably they forbid combining marks. They sometimes exclude other values (such as bidi controls, although those are excluded above). I think using the HTML restrictions is a realistic solution for CSS for the reasons given above. 

We might need a note about combining mark handling at the start of a token. HTML handles this by requiring an alpha char (`[a-zA-Z]` in your case) at the start (HTML also treats combining characters as non-combining when parsing, e.g. `class="́"` contains a class name consisting solely of a combining mark. (I used an entity for visibility). As long as the processor can't be fooled, I think you're good to go?

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


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

Received on Wednesday, 16 March 2022 18:16:06 UTC