- From: Roman Komarov via GitHub <noreply@w3.org>
- Date: Wed, 16 Jul 2025 15:52:24 +0000
- To: public-css-archive@w3.org
Dashes allow us to differentiate built-in idents from user-defined custom idents. You can expect every new user-defined idents to have them in the beginning; see the idents in anchor positioning and scroll-driven animations — all user-defined idents there are dashed. Some older specs (like view transitions) still had them not dashed, but from now on we will just have to get used to it. Having these dashes allows us to make the syntax of various places in CSS much more flexible and order-independent to evade cases like with the `animation` shorthand. And — it also allows us, as authors, to more easily tell apart what is a custom ident or not. I advocate starting to use [dashed idents for everything](https://blog.kizu.dev/dashed-idents-for-everything/), as any place that accepts custom idents (animation names, counter names, etc.) also accept dashed idents. Then, you will get used for them to be present not just in custom properties, but in other places, and you will eventually get used to it. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-3079245030 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 July 2025 15:52:25 UTC