Many webpages contain several sections which are independent of each other. For example a listing of article headlines and content, as in the markup below.

<h1>My blog</h1>
<article>
  <h2>Heading of a nice article</h2>
  <p>Content here.</p>
</article>
<article>
  <h2>Another heading of another article</h2>
  <p>More content here.</p>
</article>

Each article has the contain property with a value of content applied in the CSS.

article {
  contain: content;
}

Each article is independent of the other articles on the page, and so they have been given contain: content to indicate to the browser that this is the case. The browser can then use this information to make decisions about how to render the content. For example, it might not render articles that are outside the viewable area.

If we give each <article> the contain property with a value of content, when new elements are inserted the browser does not need to recalculate layout or repaint any area outside of the containing element's subtree. If the <article> is styled such that its size depends on its contents (e.g. with height: auto), then the browser may need to account for its size changing.

We have told it by way of the contain property that each article is independent.

The content value is shorthand for contain: layout paint style. It tells the browser that the internal layout of the element is totally separate from the rest of the page, and that everything about the element is painted inside its bounds. Nothing can visibly overflow.

This information is something that is usually known, and in fact quite obvious, to the web developer creating the page. However browsers cannot guess at your intent and cannot assume that an article will be entirely self-contained. Therefore this property gives you a nice way to explain to the browser this fact, and allow it to make performance optimizations based on that knowledge.

The values for the contain property indicate the type of containment that you want to apply to that element.

Layout containment

article {
  contain: layout;
}

Layout is normally scoped to the entire document, which means that if you move one element the entire document needs to be treated as if things could have moved anywhere. By using contain: layout you can tell the browser it only needs to check this element — everything inside the element is scoped to that element and does not affect the rest of the page, and the containing box establishes an independent formatting context.

In addition:

• float layout will be performed independently.
• Margins won't collapse across a layout containment boundary
• The layout container will be a containing block for absolute/fixed position descendants.
• The containing box creates a stacking context, therefore z-index can be used.

Paint containment

article {
  contain: paint;
}

Paint containment essentially clips the box to the padding edge of the principal box. There can be no visible overflow. The same things are true for paint containment as layout containment (see above).

Another advantage is that if the containing box is offscreen, the browser does not need to paint its contained elements — these must also be offscreen as they are contained completely by that box.

Size containment

article {
  contain: size;
}

Size containment does not offer much in the way of performance optimizations when used on its own. However, it means that the size of the element's children cannot affect the size of the element itself — its size is computed as if it had no children.

If you turn on contain: size you need to also specify the size of the element you have applied this to using contain-intrinsic-size (or the equivalent longhand properties). It will end up being zero-sized in most cases, if you don't manually give it a size.

Style containment

article {
  contain: style;
}

Despite the name, style containment does not provide scoped styles such as you would get with the Shadow DOM. The main use case is to prevent situations where a CSS Counter could be changed in an element, which could then affect the rest of the tree.

Using contain: style would ensure that the counter-increment and counter-set properties created new counters scoped to that subtree only.

Special values

There are two special values of contain:

• content
• strict

We encountered the first in the example above. Using contain: content turns on layout and paint containment. The specification describes this value as being "reasonably safe to apply widely". It does not apply size containment, so you would not be at risk of a box ending up zero-sized due to a reliance on the size of its children.

To gain as much containment as possible use contain: strict, which behaves the same as contain: size layout paint style:

contain: strict;

content-visibility controls whether or not an element renders its contents at all, along with forcing a strong set of containments, allowing user agents to potentially omit large swathes of layout and rendering work until it becomes needed. Basically it enables the user agent to skip an element's rendering work (including layout and painting) until it is needed — which makes the initial page load much faster.

Its possible values are:

• visible: The default behavior — an element's contents are laid out and rendered as normal.
• hidden: The element skips its contents. The skipped contents must not be accessible to user agent features such as find-in-page, tab-order navigation, etc., nor be selectable or focusable.
• auto: The element turns on layout containment, style containment, and paint containment. If the element is not relevant to the user, it also skips its contents. Unlike hidden, the skipped contents must still be available as normal to user-agent features such as find-in-page, tab order navigation, etc., and must be focusable and selectable as normal.

The specification refers to the concept of relevant to the user. An element that is relevant to the user should be rendered, as it is visible, and/or being interacted with by the user.

To be precise, an element is relevant to the user if any of the following are true:

• The element appears in the viewport, or a user-agent-defined margin around the viewport (50% of the viewport dimensions, to give the app time to prepare for when the element visibility changes).
• The element or its contents receive focus.
• The element or its contents are selected, for example by dragging over the text with the mouse cursor or by some other highlight operation.
• The element or its contents are placed in the top layer.

The specification refers to the concept of skips its contents. This means that the element referred to is not relevant to the user and will not be rendered to improve performance.

To be precise, when an element skips its contents:

• It has layout, style, paint, and size containment turned on.
• Its contents are not painted, as if visibility: hidden was set on it.
• Its contents do not receive pointer events, as if pointer-events: none was set on it.

• contain
• content-visibility

• An Introduction to CSS Containment
• The contentvisibilityautostatechange event