Handling optional custom property values ??in multi-valued CSS properties such as transform
requires sometimes some tricks. Suppose you have an element whose transform
attribute contains multiple values:
.el { transform: translate(100px) scale(1.5) skew(5deg); }
If you want to apply only certain transform values ??as needed, you can use custom properties to achieve optionality:
.el { /* |-- default ---| |-- optional --| */ transform: translate(100px) var(--transform); }
However, if --transform
is not defined, the entire transform
property will be invalid. The solution is to use a null value as the fallback value:
.el { transform: translate(100px) var(--transform, ); }
Pay attention to the difference? Here a null value ( ,
) is defined as a fallback. According to the specification:
Unlike the usual comma omission rule (which requires omitting when commas do not separate values), in
var()
, a separate comma (nothing afterwards) must be considered valid, indicating an empty fallback value.
This is similar to the CSS custom property switching technique, which utilizes custom properties to have space values.
Demo
This trick works with any multi-valued CSS attribute. In addition to transform
, the following demonstration also uses text-shadow
, background
, and filter
.
For some properties that accept multiple values ??(such as text-shadow
), special handling is required since they only apply to comma separators. In these cases, when defining a CSS custom property, you (as the code author) know that it is only used in the context of the custom property's defined value. Then you should insert a comma directly before the first value in the custom property, like so:
--text-shadow: ,0 0 5px black;
Of course, this limits the ability to use this variable if the attribute value is unique. However, this can be solved by creating a "layer" of variables, i.e. custom properties point to a lower level custom properties.
Note the Sass compiler
While exploring this trick, I found that there is a bug in the Sass compiler that removes empty fallback values ??( ,
), which is not consistent with the specification. I've reported this error and hope it will be fixed soon.
As a temporary workaround, you can use fallback values ??that do not cause rendering, for example:
transform: translate(100px) var(--transform, scale(1));
The above is the detailed content of Neat Optional Custom Property Values Trick. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

Theconic-gradient()functioninCSScreatescirculargradientsthatrotatecolorstopsaroundacentralpoint.1.Itisidealforpiecharts,progressindicators,colorwheels,anddecorativebackgrounds.2.Itworksbydefiningcolorstopsatspecificangles,optionallystartingfromadefin
