This CSS module describes how to collate style rules and assign values to all properties on all elements. By way of cascading and inheritance, values are propagated for all properties on all elements.
CSS is a language for describing the rendering of structured documents
(such as HTML and XML)
on screen, on paper, etc.
Status of this document
This is a public copy of the editors’ draft.
It is provided for discussion only and may change at any moment.
Its publication here does not imply endorsement of its contents by W3C.
Don’t cite this document other than as work in progress.
Please send feedback
by filing issues in GitHub (preferred),
including the spec code “css-cascade” in the title, like this:
“[css-cascade] …summary of comment…”.
All issues and comments are archived.
Alternately, feedback can be sent to the (archived) public mailing list www-style@w3.org.
This is a diff spec over CSS Cascading and Inheritance Level 6.
It is currently an Exploratory Working Draft:
if you are implementing anything, please use Level 6 as a reference.
We will merge the Level 6 text into this draft once it reaches CR.
the optional <sheet-name-list> imports only the stylesheet(s)
with names matching named stylesheets from the provided URL
in the order they are listed.
the optional layer keyword or layer() function
assigns the contents of the stylesheet into its own anonymous cascade layer or into the named cascade layer.
The layer is added to the layer order
even if the import fails to load the stylesheet,
but is subject to any import conditions (just as if declared by an @layer rule wrapped
in the appropriate conditional group rules).
@import foo from url("narrow.css") supports(display: flex) handheld and (max-width: 400px);
The following layer imports the named stylesheets named "foo" and "bar" from "tabs.css" into
the framework.component layer, and an un-named layer, respectively:
@import foo, bar from url("tabs.css") layer(framework.component);
@import foo, bar from url("override.css") layer;
If a <url-string> is provided,
it must be interpreted as a <url> with the same value.
The following lines are equivalent in meaning
and illustrate both @import syntaxes
(one with url() and one with a bare string):
The following features have been added since Level 4:
Added cascade layers to the cascade sort criteria
(and defined style attributes as a distinct step of the cascade sort criteria
so that they interact appropriately).
Introduced the @layer rule for defining cascade layers.
Incorporation of animations and transitions into the cascade.
Acknowledgments
David Baron,
Tantek Çelik,
Keith Grant,
Giuseppe Gurgone,
Theresa O’Connor,
Florian Rivoal,
Noam Rosenthal,
Simon Sapin,
Jen Simmons,
Nicole Sullivan,
Lea Verou,
and Boris Zbarsky
contributed to this specification.
5. Privacy Considerations
User preferences and UA defaults expressed via application of style rules
are exposed by the cascade process,
and can be inferred from the computed styles they apply to a document.
6. Security Considerations
The cascade process does not distinguish between same-origin and cross-origin stylesheets,
enabling the content of cross-origin stylesheets to be inferred
from the computed styles they apply to a document.
The @import rule does not apply the CORS protocol to loading cross-origin stylesheets,
instead allowing them to be freely imported and applied.
The @import rule assumes that resources without Content-Type metadata (or any same-origin file if the host document is in quirks mode)
are text/css,
potentially allowing arbitrary files to be imported into the page
and interpreted as CSS,
potentially allowing sensitive data to be inferred from the computed styles they apply to a document.
Conformance
Document conventions
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.
Tests
Tests relating to the content of this specification
may be documented in “Tests” blocks like this one.
Any such block is non-normative.
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.
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 component 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,
non-experimental implementations are possible, and implementors should
release an unprefixed implementation of any CR-level feature they
can demonstrate to be correctly implemented according to spec.
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.
This is a diff spec over CSS Cascading and Inheritance Level 6.
It is currently an Exploratory Working Draft:
if you are implementing anything, please use Level 6 as a reference.
We will merge the Level 6 text into this draft once it reaches CR. ↵
Firefox27+Safari9.1+Chrome37+Opera?Edge79+Edge (Legacy)?IENoneFirefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
Firefox1+Safari1+Chrome1+Opera4+Edge79+Edge (Legacy)12+IE8+Firefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
Firefox19+Safari1.2+Chrome1+Opera?Edge79+Edge (Legacy)13+IENoneFirefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
Firefox67+Safari9.1+Chrome84+Opera?Edge84+Edge (Legacy)?IENoneFirefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
Firefox27+Safari9.1+Chrome41+Opera?Edge79+Edge (Legacy)13+IENoneFirefox for Android?iOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?