- Published on:
- Categories:
- css variables&Very ThinSpace;9css&Very ThinSpace;85
- Immediate Music:
- Rökkurró ,
Sjónarspil
- Current Drink:
- Ceylon Tea
TPAC 2025 just ended, and I’m definitely tired. Participating in this from a distance, my sleep schedule is out of whack right now. I have several ideas for CSS-related posts on my list of ideas for November, but almost all of them require at least some amount of research and crafting demos.
Well! I found a note I wanted to expand on, and which seems small enough that I can finish it in its changed state.
I repeat the title of this post: Is it okay to say “CSS variables” instead of (or along with) “custom properties”,
I wouldn’t say it’s something controversial, but it was always something where I always had to stumble a little bit before continuing to use the terminology.
The official name of the related CSS module is “CSS Custom Properties for Cascading Variables”. Its URL is Slug css-variables,
they are variableMore specifically: Comprehensive Variable. They change with cascades: when different rules match, values can be overridden and changed.
We can have animations that involve custom properties, or custom properties with values based on viewport, container, or anything else – dynamic, responsive values that can vary For many reasons.
they are Too Custom properties, and even more properties when using—e.g. @propertyThey can also be typed explicitly, while the rest of CSS is often typed implicitly, But – unlike some other “programming languages”, typed,
Ah, yes, CSS (and HTML) Are programming Languages, and anyone who thinks otherwise is wrong. Best Well, according to me, programming languages.
Oh, I’m tired. But even after finishing it last Day of csswg F2FI’ve successfully experimented a bit with an idea I’m running, and now plan to write a reasonably good article for my main site, as I sometimes do. Stay in touch.
<a href