--- title: Introducción a CSS en cascada slug: Web/CSS/Cascade translation_of: Web/CSS/Cascade ---
Solo las declaraciones CSS, es decir pares de propiedad/valor, participan en la cascada. Esto significa que las at-rules que contienen entidades distintas de las declaraciones, como una regla @font-face
que contiene descriptores, no participan en la cascada. En estos casos, solo la regla-at en su conjunto participa en la cascada: aquí, la @font-face
identificada por su descriptor de familia de tipografías. Si se definen varias reglas @font-face
con el mismo descriptor, solo se considera la @font-face
, como conjunto, más adecuada.
Mientras que las declaraciones contenidas en la mayoría de las reglas-at -como aquellas en @media
, @document o @support - participan en la cascada, las declaraciones contenidas en @keyframes no. Como con @font-face, solo la regla-at en su conjunto se selecciona a través del algoritmo en cascada.
Finalmente, debemos tener en cuenta que {{cssxref ("@ import")}} y {{cssxref ("@ charset")}} obedecen a algoritmos específicos y no se ven afectados por el algoritmo en cascada.
The CSS cascade algorithm's job is to select CSS declarations in order to determine the correct values for CSS properties. CSS declarations originate from different origins: the {{anch("User-agent stylesheets")}}, the {{anch("Author stylesheets")}}, and the {{anch("User stylesheets")}}.
Though style sheets come from these different origins, they overlap in scope; to make this work, the cascade algorithm defines how they interact.
The browser has a basic style sheet that gives a default style to any document. These style sheets are named user-agent stylesheets. Some browsers use actual style sheets for this purpose, while others simulate them in code, but the end result is the same.
Some browsers let users modify the user-agent stylesheet. Although some constraints on user-agent stylesheets are set by the HTML specification, browsers still have a lot of latitude: that means that significant differences exist from one browser to another. To simplify the development process, Web developers often use a CSS reset style sheet, forcing common properties values to a known state before beginning to make alterations to suit their specific needs.
Author stylesheets are the most common type of style sheet. These are style sheets that define styles as part of the design of a given web page or site. The author of the page defines the styles for the document using one or more stylesheets, which define the look and feel of the website — its theme.
The user (or reader) of the web site can choose to override styles in many browsers using a custom user stylesheet designed to tailor the experience to the user's wishes.
The cascading algorithm determines how to find the value to apply for each property for each document element.
!important
, and by their origin. The cascade is in ascending order, which means that !important
values from a user-defined style sheet have precedence over normal values originated from a user-agent style sheet:
Origin | Importance | |
---|---|---|
1 | user agent | normal |
2 | user | normal |
3 | author | normal |
4 | animations | |
5 | author | !important |
6 | user | !important |
7 | user agent | !important |
8 | transitions |
After your content has finished altering styles, it may find itself in a situation where it needs to restore them to a known state. This may happen in cases of animations, theme changes, and so forth. The CSS property {{cssxref("all")}} lets you quickly set (almost) everything in CSS back to a known state.
all
lets you opt to immediately restore all properties to any of their initial (default) state, the state inherited from the previous level of the cascade, a specific origin (the user-agent stylesheet, the author stylesheet, or the user stylesheet), or even to clear the values of the properties entirely.
CSS animations, using {{ cssxref("@keyframes")}} at-rules, define animations between states. Keyframes don't cascade, meaning that at any given time CSS takes values from only one single {{cssxref("@keyframes")}}, and never mixes multiple ones together.
When several keyframes are appropriate, it chooses the latest defined in the most important document, but never combined all together.
Let's look at an example involving multiple sources of CSS across the various origins; here we have a user agent style sheet, two author style sheets, a user stylesheet, and inline styles within the HTML:
User-agent CSS:
li { margin-left: 10px }
Author CSS 1:
li { margin-left: 0 } /* This is a reset */
Author CSS 2:
@media screen { li { margin-left: 3px } } @media print { li { margin-left: 1px } }
User CSS:
.specific { margin-left: 1em }
HTML:
<ul> <li class="specific">1<sup>st</sup></li> <li>2<sup>nd</sup></li> </ul>
In this case, declarations inside li
and .specific
rules should apply. No declaration is marked as !important
, so the precedence order is author style sheets before user style sheets or user-agent stylesheet.
So three declarations are in competition:
margin-left: 0
margin-left: 3px
margin-left: 1px
The last one is ignored (on a screen), and the first two have the same selector, hence the same specificity. Therefore, it is the last one that is then selected:
margin-left: 3px
Note that the declaration defined in the user CSS, though having a greater specificity, is not chosen as the cascade algorithm is applied before the specificity algorithm.
Specification | Status | Comment |
---|---|---|
{{SpecName("CSS4 Cascade")}} | {{Spec2("CSS4 Cascade")}} | Added the {{CSSxRef("revert")}} keyword, which allows rolling a property back a cascade level. |
{{SpecName("CSS3 Cascade")}} | {{Spec2("CSS3 Cascade")}} | Removed the override cascade origin, as it was never used in a W3C standard. |
{{SpecName("CSS2.1", "cascade.html", "the cascade")}} | {{Spec2("CSS2.1")}} | |
{{SpecName("CSS1", "#the-cascade", "the cascade")}} | {{Spec2("CSS1")}} | Initial definition. |