This specification has been abandoned, due to being generally a bad idea. The reasoning is explained in this blog post. It is not expected to be revived.
This specification defines the @apply rule, which allows an author to store a set of properties in a named variable, then reference them in other style rules.
CSS is a language for describing the rendering of structured documents
(such as HTML and XML)
on screen, on paper, in speech, etc.
Status of this document
1. Introduction
CSS custom properties enable authors to define reusable values,
give them names,
then invoke them throughout the stylesheet.
This makes it easy to keep a page’s theme consistent when changes are made,
because the theming values are defined in a central place.
But custom properties can hold more than just values—they can also be used to hold sets of declarations.
The @apply rule takes these sets of declarations and inlines them in another style rule,
serving a purpose analogous to what the var() function does for individual values.
There are many ways to apply sets of declarations to an element.
In particular, the common way is to just create a style rule,
and apply it to the desired elements via a selector.
However, this requires the elements you wish to target to already have the right features for a selector,
or else you have to alter your markup,
or write a complex selector that targets them precisely with their varied features
(and which needs to be maintained as you alter the page markup and change the selectors targetting those elements).
This also requires careful management of specificity,
as the rule has to interact with the existing rules styling the elements.
The @apply rule allows this reuse to be inlined into the existing selectors you’re already using,
reducing the amount of effort required to keep your stylesheet consistent as things change in the page.
It also avoids the need to manage specificity any more than you already do,
as the properties are inlined alongside the existing properties,
in your existing style rules.
2. Defining Custom Sets of Properties
To define a custom property set for use with @apply,
you simply use a custom property with a value of a {}-wrapped block of properties.
For example, one might define a toolbar theme as a custom property set on the root element of the document,
and use it on your toolbars:
We don’t have to worry about the internal structure of the toolbars,
or precisely what internal elements use the styles.
Simply overriding the custom property will automatically do the right thing.
The #bar rule will win due to having a higher specificity,
so its color:blue rule will apply to the element,
but the background:white rule from the .foo rule also applies,
since the #bar rule did not override background.
Then when an element uses the --my-themecustom property set,
it will receive only the color:blue declaration.
The background:white declaration from the .foo rule is ignored completely,
as its rule lost the specificity battle.
Need some way to let you opt into cascading when you want it.
2.1. Changes to Custom Property Processing
If the value of a custom property contains an @apply rule,
the @apply rule must be valid according to the specified @apply grammar.
If not, the custom property is invalid and must be ignored.
For this purpose, an @apply rule is composed of a sequence of tokens
starting with the @apply token,
and ending at (and including) the first same-level semicolon,
the end of the simple block the @apply token is in,
or the end of the custom property’s value.
The @apply rule is only valid inside of a style rule.
Using it outside of a style rule,
or inside any other rule,
is invalid and causes the @apply to be ignored.
For the purposes of the cascade,
the @apply rule must be treated as if it were replaced by the properties
in the custom property set that is the value of the custom property it references.
Note: Within the CSSOM, the @apply rule is not replaced;
examining the style rule will show it as having the @apply rule in its .childRules attribute,
and the properties in the custom property set will not be visible in any way.
If the custom property that the @apply rule references
does not define a valid custom property set,
the @apply rule is treated, for the purposes of the cascade, as if it were replaced with nothing.
It is not invalid, however.
(For example, it is not dropped from the CSSOM.)
Conformance requirements are expressed with a combination of
descriptive assertions and RFC 2119 terminology. The key words “MUST”,
“MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
“RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
document are to be interpreted as described in RFC 2119.
However, for readability, these words do not appear in all uppercase
letters in this specification.
All of the text of this specification is normative except sections
explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for example”
or are set apart from the normative text with class="example",
like this:
This is an example of an informative example.
Informative notes begin with the word “Note” and are set apart from the
normative text with class="note", like this:
Note, this is an informative note.
Advisements are normative sections styled to evoke special attention and are
set apart from other normative text with <strong class="advisement">, like
this: UAs MUST provide an accessible alternative.
Conformance classes
Conformance to this specification
is defined for three conformance classes:
A style sheet is conformant to this specification
if all of its statements that use syntax defined in this module are valid
according to the generic CSS grammar and the individual grammars of each
feature defined in this module.
A renderer is conformant to this specification
if, in addition to interpreting the style sheet as defined by the
appropriate specifications, it supports all the features defined
by this specification by parsing them correctly
and rendering the document accordingly. However, the inability of a
UA to correctly render a document due to limitations of the device
does not make the UA non-conformant. (For example, a UA is not
required to render color on a monochrome monitor.)
An authoring tool is conformant to this specification
if it writes style sheets that are syntactically correct according to the
generic CSS grammar and the individual grammars of each feature in
this module, and meet all other conformance requirements of style sheets
as described in this module.
Requirements for Responsible Implementation of CSS
The following sections define several conformance requirements
for implementing CSS responsibly,
in a way that promotes interoperability in the present and future.
Partial Implementations
So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid
(and ignore as appropriate)
any at-rules, properties, property values, keywords, and other syntactic constructs
for which they have no usable level of support.
In particular, user agents must not selectively ignore
unsupported property values and honor supported values in a single multi-value property declaration:
if any value is considered invalid (as unsupported values must be),
CSS requires that the entire declaration be ignored.
Implementations of Unstable and Proprietary Features
Once a specification reaches the Candidate Recommendation stage,
implementers should release an unprefixed implementation
of any CR-level feature they can demonstrate
to be correctly implemented according to spec,
and should avoid exposing a prefixed variant of that feature.
To establish and maintain the interoperability of CSS across
implementations, the CSS Working Group requests that non-experimental
CSS renderers submit an implementation report (and, if necessary, the
testcases used for that implementation report) to the W3C before
releasing an unprefixed implementation of any CSS features. Testcases
submitted to W3C are subject to review and correction by the CSS
Working Group.