Title: CSS Containment Module Level 2
Level: 2
Shortname: css-contain
Status: ED
Work Status: stable
Group: csswg
ED: https://drafts.csswg.org/css-contain-2/
Previous Version: https://www.w3.org/TR/2022/WD-css-contain-2-20220917/
Previous Version: https://www.w3.org/TR/2020/WD-css-contain-2-20201216/
Previous Version: https://www.w3.org/TR/2020/WD-css-contain-2-20200603/
Previous Version: https://www.w3.org/TR/2019/WD-css-contain-2-20191111/
Previous Version: https://www.w3.org/TR/2019/WD-css-contain-2-20191015/
TR: https://www.w3.org/TR/css-contain-2/
Editor: Tab Atkins, Google, http://xanthir.com/contact/, w3cid 42199
Editor: Florian Rivoal, On behalf of Bloomberg, https://florian.rivoal.net/, w3cid 43241
Editor: Vladimir Levin, Google, vmpstr@google.com, w3cid 75295
Abstract: This CSS module describes the 'contain' property, which indicates that the element's subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
Test Suite: https://test.csswg.org/harness/results/css-contain-1_dev/
WPT Path Prefix: css/css-contain/
Efficiently rendering a website relies on the user agent being able to detect what parts of the page are being displayed,
which parts might affect the currently-displayed section,
and what can be ignored.
There are various heuristics that can be used to guess when a given sub-tree is independent of the rest of the page in some manner,
but they're fragile,
so innocuous changes to a page may inadvertently make it fail such heuristic tests,
causing rendering to fall into a slow code path.
There are also many things that would be good to isolate which are difficult or impossible to detect in a heuristic manner.
To alleviate these problems
and allow strong, predictable isolation of a subtree from the rest of the page,
this specification defines a 'contain' property.
To allow even further optimization of off-screen contents,
this spec also defines a 'content-visibility' property,
enabling the user agent to skip an element's layout and painting entirely when not needed.
Module Interactions
This document defines new features not present in earlier specifications.
In addition, it aims to replace and supersede [[!CSS-CONTAIN-1]]
once stable.
Value Definitions
This specification follows the CSS property definition conventions from [[!CSS2]]
using the value definition syntax from [[!CSS-VALUES-3]].
Value types not defined in this specification are defined in CSS Values & Units [[!CSS-VALUES-3]].
Combination with other CSS modules may expand the definitions of these value types.
In addition to the property-specific values listed in their definitions,
all properties defined in this specification
also accept the CSS-wide keywords as their property value.
For readability they have not been repeated explicitly.
Name: contain
Value: none | strict | content | [ [size | inline-size] || layout || style || paint ]
Initial: none
Inherited: no
Applies to: See below
Computed value: the keyword ''contain/none'' or one or more of ''size'', ''layout'', ''paint''
Animation type: not animatable
User agents are expected to support this property on all media, including non-visual ones.
The 'contain' property allows an author to indicate that an element and its contents are,
as much as possible,
independent of the rest of the document tree.
This allows user agents to utilize much stronger optimizations when rendering a page using 'contain' properly,
and allows authors to be confident that their page won't accidentally fall into a slow code path
due to an innocuous change.
none
This value indicates that the property has no effect.
The element renders as normal,
with no containment effects applied.
strict
This value computes to ''size layout paint style'',
and thus turns on all forms of containment for the element.
contain-strict-001.html
contain-strict-002.html
contain-strict-003.html
contain-strict-011.html
contain-flexbox-outline.html
content
This value computes to ''layout paint style'',
and thus turns on all forms of containmentexceptsize containment for the element.
contain-content-001.html
contain-content-002.html
contain-content-003.html
contain-content-004.html
contain-content-011.html
Note: ''contain: content'' is reasonably "safe" to apply widely;
its effects are fairly minor in practice,
and most content won't run afoul of its restrictions.
However, because it doesn't apply size containment,
the element can still respond to the size of its contents,
which can cause layout-invalidation to percolate further up the tree than desired.
Use ''contain: strict'' when possible,
to gain as much containment as you can.
size
The value turns on size containment for the element.
This ensures that the [=size containment box|containment box=] can be laid out
without needing to examine its descendants.
contain-size-001.html
contain-size-002.html
contain-size-003.html
contain-size-004.html
contain-size-005.html
contain-size-006.html
contain-size-007.html
contain-size-008.html
contain-size-009.html
contain-size-010.html
contain-size-011.html
contain-size-012.html
contain-size-012b.html
contain-size-013.html
contain-size-021.html
contain-size-023.html
contain-size-025.html
contain-size-027.html
contain-size-041.html
contain-size-042.html
contain-size-051.html
contain-size-052.html
contain-size-056.html
contain-size-061.html
contain-size-062.html
contain-size-063.html
contain-size-baseline-001.html
contain-size-borders.html
contain-size-breaks-001.html
contain-size-button-001.html
contain-size-fieldset-001.html
contain-size-fieldset-002.html
contain-size-flexbox-001.html
contain-size-flexbox-002.html
contain-size-grid-001.html
contain-size-grid-002.html
contain-size-grid-003.html
contain-size-grid-004.html
contain-size-grid-005.html
contain-size-grid-006.html
contain-size-monolithic-001.html
contain-size-monolithic-002.html
contain-size-multicol-001.html
contain-size-multicol-as-flex-item.html
contain-size-replaced-001.html
contain-size-replaced-002.html
contain-size-replaced-003a.html
contain-size-replaced-003b.html
contain-size-replaced-003c.html
contain-size-replaced-004.html
contain-size-replaced-005.html
contain-size-replaced-006.html
contain-size-replaced-007.html
contain-size-select-001.html
contain-size-select-002.html
contain-size-scrollbars-001.html
contain-size-scrollbars-002.html
contain-size-scrollbars-003.html
contain-size-scrollbars-004.html
contain-layout-size-003.html
contain-paint-size-001.html
contain-paint-size-002.html
contain-paint-size-003.html
contain-size-removed.html
contain-size-dynamic-001.html
contain-size-grid-indefinite-height-min-height-flex-row.html
contain-size-grid-stretches-auto-rows.html
inline-size
This value turns on [=inline-size containment=] for the element.
This prevents the [=inline-size=] of its [=principal box=]
from directly depending on its contents.
contain-inline-size-bfc-floats-001.html
contain-inline-size-bfc-floats-002.html
contain-inline-size-fieldset.html
contain-inline-size-flex.html
contain-inline-size-flexitem.html
contain-inline-size-grid.html
contain-inline-size-intrinsic.html
contain-inline-size-legend.html
contain-inline-size-multicol.html
contain-inline-size-regular-container.html
contain-inline-size-removed.html
contain-inline-size-replaced.html
contain-inline-size-table.html
contain-inline-size-vertical-rl-.html
contain-inline-size-grid-indefinite-height-min-height-flex-row.html
contain-inline-size-grid-stretches-auto-rows.html
Note: There can still be indirect dependencies,
see [[#containment-inline-size]].
layout
This value turns on layout containment for the element.
This ensures that the [=layout containment box|containment box=] is totally opaque for layout purposes;
nothing outside can affect its internal layout,
and vice versa.
contain-layout-001.html
contain-layout-002.html
contain-layout-003.html
contain-layout-004.html
contain-layout-005.html
contain-layout-006.html
contain-layout-007.html
contain-layout-009.html
contain-layout-010.html
contain-layout-011.html
contain-layout-012.html
contain-layout-013.html
contain-layout-014.html
contain-layout-016.html
contain-layout-017.html
contain-layout-018.html
contain-layout-019.html
contain-layout-020.html
contain-layout-021.html
contain-layout-baseline-001.html
contain-layout-baseline-002.html
contain-layout-baseline-003.html
contain-layout-baseline-004.html
contain-layout-baseline-005.html
contain-layout-breaks-001.html
contain-layout-breaks-002.html
contain-layout-cell-001.html
contain-layout-cell-002.html
contain-layout-flexbox-001.html
contain-layout-grid-001.html
contain-layout-ifc-022.html
contain-layout-independent-formatting-context-001.html
contain-layout-independent-formatting-context-002.html
contain-layout-independent-formatting-context-003.html
contain-layout-ink-overflow-013.html
contain-layout-ink-overflow-014.html
contain-layout-ink-overflow-015.html
contain-layout-ink-overflow-016.html
contain-layout-ink-overflow-017.html
contain-layout-ink-overflow-018.html
contain-layout-ink-overflow-019.html
contain-layout-ink-overflow-020.html
contain-layout-size-003.html
contain-subgrid-001.html
contain-layout-dynamic-001.html
contain-layout-dynamic-004.html
contain-layout-dynamic-005.html
style
This value turns on style containment for the element.
This ensures that,
for properties which can have effects on more than just an element and its descendants,
those effects don't escape the element.
contain-style-baseline-001.html
contain-style-breaks-001.html
contain-style-breaks-002.html
contain-style-breaks-003.html
contain-style-breaks-004.html
contain-style-breaks-005.html
contain-style-counters-001.html
contain-style-counters-002.html
contain-style-counters-003.html
contain-style-counters-004.html
contain-style-counters-005.html
contain-style-ol-ordinal-li-container.html
contain-style-ol-ordinal-pseudo-reversed.html
contain-style-ol-ordinal-pseudo.html
contain-style-ol-ordinal-reversed.html
contain-style-ol-ordinal-start-reversed.html
contain-style-ol-ordinal-start.html
contain-style-ol-ordinal.html
counter-scoping-001.html
counter-scoping-002.html
counter-scoping-003.html
counter-scoping-004.html
quote-scoping-001.html
quote-scoping-002.html
quote-scoping-003.html
quote-scoping-004.html
quote-scoping-invalidation-001.html
quote-scoping-invalidation-002.html
quote-scoping-invalidation-003.html
quote-scoping-invalidation-004.html
contain-style-dynamic-001.html
paint
This value turns on paint containment for the element.
This ensures that the descendants of the [=paint containment box|containment box=] don't display outside its bounds,
so if an element is off-screen or otherwise not visible,
its descendants are also guaranteed to be not visible.
contain-paint-001.html
contain-paint-002.html
contain-paint-004.html
contain-paint-005.html
contain-paint-006.html
contain-paint-007.html
contain-paint-008.html
contain-paint-009.html
contain-paint-010.html
contain-paint-011.html
contain-paint-012.html
contain-paint-014.html
contain-paint-015.html
contain-paint-016.html
contain-paint-017.html
contain-paint-018.html
contain-paint-019.html
contain-paint-020.html
contain-paint-021.html
contain-paint-022.html
contain-paint-023.html
contain-paint-024.html
contain-paint-025.html
contain-paint-047.html
contain-paint-048.html
contain-paint-baseline-001.html
contain-paint-cell-001.html
contain-paint-cell-002.html
contain-paint-clip-011.html
contain-paint-clip-012.html
contain-paint-clip-013.html
contain-paint-clip-014.html
contain-paint-clip-015.html
contain-paint-clip-016.html
contain-paint-clip-017.html
contain-paint-clip-018.html
contain-paint-clip-019.html
contain-paint-ifc-011.html
contain-paint-independent-formatting-context-001.html
contain-paint-independent-formatting-context-002.html
contain-paint-independent-formatting-context-003.html
contain-paint-size-001.html
contain-paint-size-002.html
contain-paint-size-003.html
contain-paint-table-001.html
contain-paint-table-002.html
contain-subgrid-001.html
contain-paint-change-opacity.html
contain-paint-dynamic-001.html
contain-paint-dynamic-002.html
contain-paint-dynamic-003.html
contain-paint-dynamic-004.html
contain-paint-dynamic-005.html
This property generally applies to all elements (including [[css-pseudo-4#generated-content]]),
although some types of containment have no effect on some elements,
as detailed in [[#containment-types]].
In addition, in the case of [[SVG2]],
the 'contain' property only applies to <{svg}> elements that have an associated CSS layout box.
'contain' is useful when used widely on a page,
particularly when a page contains a lot of "widgets" which are all independent.
For example, assume a micropost social network had markup something like this:
<body>
<aside>...</aside>
<section>
<h2>Messages</h2>
<article>
Lol, check out this dog: images.example.com/jsK3jkl
</article>
<article>
I had a ham sandwich today. #goodtimes
</article>
<article>
I have political opinions that you need to hear!
</article>
…
</section>
</body>
There are probably a lot of messages displayed on the site,
but each is independent and won't affect anything else on the site.
As such, each can be marked with ''contain: content'' to communicate this to the user agent,
so it can optimize the page and skip a lot of computation for messages that are off-screen.
If the size of each message is known ahead of time,
''contain: strict'' can be applied to communicate further restrictions.
Additionally, when any [=containments=] are active
on either the HTML <{html}> or <{body}> elements,
propagation of properties
from the <{body}> element
to the [=initial containing block=], the viewport, or the [=canvas background=],
is disabled.
Notably, this affects:
* 'writing-mode', 'direction', and 'text-orientation' (see [[CSS-WRITING-MODES-3#principal-flow]])
* 'overflow' and its longhands (see [[CSS-OVERFLOW-3#overflow-propagation]])
* 'background' and its longhands (see [[CSS-BACKGROUNDS-3#body-background]])
contain-body-bg-001.html
contain-body-bg-002.html
contain-body-bg-003.html
contain-body-bg-004.html
contain-body-dir-001.html
contain-body-dir-002.html
contain-body-dir-003.html
contain-body-dir-004.html
contain-body-overflow-001.html
contain-body-overflow-002.html
contain-body-overflow-003.html
contain-body-overflow-004.html
contain-body-t-o-001.html
contain-body-t-o-002.html
contain-body-t-o-003.html
contain-body-t-o-004.html
contain-body-w-m-001.html
contain-body-w-m-002.html
contain-body-w-m-003.html
contain-body-w-m-004.html
contain-html-bg-001.html
contain-html-bg-002.html
contain-html-bg-003.html
contain-html-bg-004.html
contain-html-dir-001.html
contain-html-dir-002.html
contain-html-dir-003.html
contain-html-dir-004.html
contain-html-overflow-001.html
contain-html-overflow-002.html
contain-html-overflow-003.html
contain-html-overflow-004.html
contain-html-t-o-001.html
contain-html-t-o-002.html
contain-html-t-o-003.html
contain-html-t-o-004.html
contain-html-w-m-001.html
contain-html-w-m-002.html
contain-html-w-m-003.html
contain-html-w-m-004.html
Note: Propagation
to the [=initial containing block=], the viewport, or the [=canvas background=],
of properties set on the <{html}> element itself
is unaffected.
Note: Several properties beyond 'contain' can turn on various [=containments=] for an element.
These do not affect the value of 'contain';
an element can have ''contain: none''
but still have [=layout containment=] turned on by 'content-visibility',
for example.
Types of Containment
There are several varieties of containment that an element can be subject to,
restricting the effects that its descendants can have on the rest of the page in various ways.
Containment enables much more powerful optimizations by user agents,
and helps authors compose their page out of functional units,
as it limits how widely a given change can affect a document.
Advisement: Specification authors introducing new properties or mechanisms
need to consider whether and how the various types of containment
affect what they are introducing,
and include in their specification any effect not described here.
Size Containment
Giving an element size containment
makes its [=principal box=] a size containment box
and has the following effects:
1.
The [=intrinsic sizes=] of the [=size containment box=]
are determined as if the element had no content,
following the same logic as when [=sizing as if empty=].
Note: This affects explicit invocations of the ''min-content'' or ''max-content'' keywords,
as well as any calculation that depends on these measurement,
such as sizing [=grid tracks=] into which a size contained item is placed,
or if [=fit-content sizing=] the containment box's parent.
contain-size-013.html
contain-size-041.html
contain-size-042.html
contain-size-replaced-001.html
contain-size-replaced-002.html
contain-size-replaced-003a.html
contain-size-replaced-003b.html
contain-size-replaced-003c.html
contain-size-replaced-004.html
contain-size-replaced-005.html
contain-size-replaced-006.html
contain-size-block-001.html
contain-size-block-002.html
contain-size-block-003.html
contain-size-block-004.html
contain-size-button-002.html
contain-size-fieldset-003.html
contain-size-flex-001.html
contain-size-grid-005.html
contain-size-grid-006.html
contain-size-inline-block-001.html
contain-size-inline-block-002.html
contain-size-inline-block-003.html
contain-size-inline-block-004.html
contain-size-inline-flex-001.html
contain-size-multicol-002.html
contain-size-multicol-003.html
contain-size-select-elem-001.html
contain-size-select-elem-002.html
contain-size-select-elem-003.html
contain-size-select-elem-004.html
contain-size-select-elem-005.html
2. Laying out a [=size containment box=] and its content is conceptually done in two phases:
Sizing as if empty
The [=used value|used=] 'width' and 'height' of the [=size containment box|containment box=]
are determined as if performing a normal layout of the box,
except that it is treated as having no content--
not even through pseudo elements such as ''::before'', ''::after'', or ''::marker''.
contain-size-021.html
contain-size-023.html
contain-size-025.html
contain-size-027.html
contain-size-061.html
contain-size-062.html
contain-size-063.html
contain-size-borders.html
contain-size-fieldset-001.html
contain-size-fieldset-002.html
contain-size-select-001.html
contain-size-select-002.html
contain-size-scrollbars-001.html
contain-size-scrollbars-002.html
contain-size-scrollbars-003.html
contain-size-scrollbars-004.html
contain-size-button-001.html
contain-size-flexbox-001.html
contain-size-flexbox-002.html
contain-size-grid-001.html
Replaced elements must be treated as having a [=natural dimensions|natural=] width and height of 0
and no [=natural aspect ratio=].
Note: Size containment only suppresses the [=natural aspect ratio=],
so properties like 'aspect-ratio' which affect that [=preferred aspect ratio=] directly
are honored.
contain-size-013.html
contain-size-041.html
contain-size-042.html
contain-size-replaced-001.html
contain-size-replaced-002.html
contain-size-replaced-003a.html
contain-size-replaced-003b.html
contain-size-replaced-003c.html
contain-size-replaced-004.html
contain-size-replaced-005.html
replaced-element-023.html
replaced-element-025.html
replaced-element-027.html
All CSS properties of the [=size containment box=] are taken into account
as they would be when performing layout normally.
Other specifications may make specific exemptions.
contain-size-replaced-006.html
Note: Even when the element's [=sizing properties=] specify an intrinsic size,
this does not necessarily make the element zero-sized:
properties set on the element itself
continue to be taken into account,
which can cause it to be larger.
contain-size-grid-002.html
contain-size-grid-003.html
contain-size-multicol-001.html
contain-size-multicol-as-flex-item.html
Laying out in-place
The [=size containment box|containment box=]'s content
(including any pseudo-elements)
must then be laid out into
the now fixed-size [=size containment box|containment box=] normally.
contain-size-064.html
Note: [=Size containment=] does not suppress baseline alignment.
See [=layout containment=] for that.
contain-size-baseline-001.html
contain-size-fieldset-004.html
contain-size-inline-block-001.html
contain-size-inline-block-002.html
contain-size-inline-block-003.html
contain-size-inline-block-004.html
contain-size-inline-flex-001.html
3. [=Size containment boxes=] are monolithic (See [[CSS-BREAK-3#possible-breaks]]).
contain-size-breaks-001.html
contain-size-monolithic-001.html
contain-size-monolithic-002.html
contain-size-multicol-004.html
Given the following markup and style, the image would be sized to 100px by 100px,
as the aspect ratio set by the 'aspect-ratio' property takes effect.
If the 'aspect-ratio' property had not been declared,
the image would have been 100px by 0px,
as its [=natural aspect ratio=] is suppressed,
and its [=natural height=] is treated as 0.
However, giving an element [=size containment=]
has no effect if any of the following are true:
* if the element does not generate a principal box
(as is the case with ''display: contents'' or ''display: none'')
* if its [=inner display type=] is ''display/table''
contain-size-012.html
contain-size-012b.html
* if its [=principal box=] is
an internal table box
contain-size-006.html
contain-size-007.html
contain-size-008.html
contain-size-009.html
contain-size-010.html
contain-size-051.html
contain-size-052.html
* if its [=principal box=] is
an internal ruby box
or a non-atomicinline-level box
contain-size-002.html
contain-size-003.html
contain-size-004.html
contain-size-005.html
contain-size-001.html
Note: Internal table boxes,
which do not include table captions,
are excluded,
because the table layout algorithm
does not allow boxes to become smaller than their inflow content.
Sizing a table cell as if it was empty and then laying out its content inside without changing the size
is effectively an undefined operation.
Manually setting the 'width' or 'height' properties to ''0''
cannot make it smaller than its content.
This concern does not apply to table captions,
which are perfectly capable of having a fixed size
that is independent of their content.
contain-size-011.html
contain-size-056.html
contain-size-table-caption-001.html
Possible Size-Containment Optimizations
This section is non-normative.
By itself, size containment does not offer much optimization opportunity.
Its primary benefit on its own is that tools which want to lay out the [=size containment box|containment box=]'s contents
based on the [=size containment box|containment box=]'s size
(such as a JS library implementing the "container query" concept)
can do so without fear of "infinite loops",
where having a child's size respond to the size of the [=size containment box|containment box=]
causes the [=size containment box|containment box=]'s size to change as well,
possibly triggering further changes in how the child sizes itself
and possibly thus more changes to the [=size containment box|containment box=]'s size,
ad infinitum.
When paired with layout containment, though,
possible optimizations that can be enabled include (but are not limited to):
1. When the style or contents of a descendant of the [=size containment box|containment box=] is changed,
calculating what part of the DOM tree is "dirtied" and might need to be re-laid out
can stop at the [=size containment box|containment box=].
2. When laying out the page,
if the [=size containment box|containment box=] is off-screen or obscured,
the layout of its contents (i.e. "[=laying out in-place=]") can be delayed or done at a lower priority.
Inline-Size Containment
Giving an element inline-size containment
applies [=size containment=] to the [=inline-axis=] sizing of its [=principal box=].
This means the [=inline-axis=] [=intrinsic sizes=] of the [=principal box=]
are determined as if the element had no content.
However, content continues to impact the box’s [=block-axis=] [=intrinsic sizes=] as usual,
and the box is allowed to [=fragmentation|fragment=] normally in the [=block axis=].
Note: In some cases,
a box’s [=block-axis=] [=intrinsic sizes=]
can impact layout in the parent [=formatting context=]
in ways that affect the box’s [=inline size=]
(e.g. by triggering scrollbars on an ancestor element),
creating a dependency of the box’s [=inline size=] on its own content.
If this changed [=inline size=] results in a different [=block size=],
that new [=block size=] can loop into further impacting the parent formatting context,
but not in a way that reverts it to the previously-problematic layout.
For example, if scrollbars were introduced,
they are then not removed,
even if the consequent [=block size=] is small enough to not need them;
or if a box’s logical height collides with a lower-placed float and is cleared down
to where it also has more available inline space
and thus becomes short enough to not have collided,
it is then not moved back up to its previous problematic size and position.
Thus, although [=inline-size containment=] prevents
the box’s content from directly affecting its [=inline size=]
through its [=inline-axis=] [=intrinsic sizes=],
its [=inline size=] can still indirectly depend on its contents
by their effect on its [=block size=].
ISSUE:
In general, the relationship between an element's inline size
and it's block size
is unpredictable and non-monotonic,
with the block size capable of shifting up and down arbitrarily
as the inline size is changed.
Infinite cycles are prevented
by ensuring that layout does not revert to a previous (known-problematic) state,
even if a naive analysis of the constraints would allow for such;
in other words, layout always “moves forward”.
We believe that current CSS layout specifications incorporate such rules,
but to the extent that they don't,
please inform the CSSWG
so that these errors can be corrected.
Consider this example,
where float placement creates a dependency of block sizes on inline sizes:
Article
Article
The block layout algorithm will first place the floating boxes,
with the first two sitting in the left and right corners of the container,
and the third, being too wide to fit between, being pushed below them.
The following article will then be laid out.
Because it is ''display: flow-root'',
it cannot intersect any floats,
and thus must take them into account
when figuring out how to size and position itself.
The layout engine first attempts to place the article
flush with the top of the container,
resulting a ''100px'' width,
plenty wide enough to accommodate its [=min-content size=].
However, due to the 'aspect-ratio' of its child,
this would cause the article to be ''100px'' tall as well,
which would intersect the third float 80px below,
so this layout opportunity is discarded.
It then attempts to position the article
flush with the top of the third float,
in the narrow ''40px''-wide space to its right.
However, since the article’s 'min-width' makes it too large
to fit in the 40px-wide space beside the third float,
it shifts below that one as well,
forming a 200px square below all the floated boxes.
Article
If the 'min-width' is removed from the article,
or if [=inline-size containment=] is added to
either the article or header
(causing ''min-width: min-content'' to resolve to zero),
then the article will fit as a 40px square
next to the final floated div
(possibly with some of its content overflowing).
At this point, the width and height of the article
(''40px'' each)
would fit back in the first considered space,
flush with the top of the container.
However, the box is not returned to the previous position,
because the layout engine knows already
that this position would result in an invalid layout.
Giving an element [=inline-size containment=]
has no effect if any of the following are true:
* if the element does not generate a principal box
(as is the case with ''display: contents'' or ''display: none'')
* if its [=inner display type=] is ''display/table''
* if its [=principal box=] is
an internal table box
* if its [=principal box=] is
an internal ruby box
or a non-atomicinline-level box
Layout Containment
Giving an element layout containment
makes its [=principal box=] a layout containment box
and has the following effects:
1. The [=layout containment box=] [=establishes an independent formatting context=].
contain-layout-ifc-022.html
contain-layout-independent-formatting-context-001.html
contain-layout-independent-formatting-context-002.html
contain-subgrid-001.html
contain-layout-formatting-context-float-001.html
contain-layout-formatting-context-margin-001.html
2. If at least one [=fragmentation container=] of a [=fragmentation context=] has [=layout containment=],
or if at least one [=fragmentation container=] of a [=fragmentation context=] is a descendant of [=layout containment box=]
and at least one subsequent [=fragmentation container=] of the same [=fragmentation context=]
is not a descendant of that same element with layout containment,
then the first [=layout containment box=]
which is either a [=fragmentation container=] itself
or is an ancestor of a [=fragmentation container=]
must “trap” the remainder of the [=fragmented flow=]:
[=fragmentation=] must not continue past the [=layout containment=] boundary,
and the last [=fragmentation container=]
within the first [=layout containment=] boundary
is treated as if it is the last [=fragmentation container=]
in its [=fragmentation context=].
If subsequent [=fragmentation containers=] in the [=fragmentation context=]
are only generated when more content remains in the [=fragmented flow=],
then they are not generated.
If they would exist regardless,
they remain part of the [=fragmentation context=],
but do not receive any content from the [=fragmented flow=].
Note: At the time of writing, no stable specification is affected by this point.
Only specifications that would enable some (but not all) fragmentation containers of a fragmentation context
to be layout-contained (or descendants of a layout contained element)
are concerned.
This is not the case of [[CSS-PAGE-3]] nor of [[CSS-MULTICOL-1]].
This requirement is nonetheless included because
several mechanisms that would make this a possibility have been considered
(e.g.: [[CSS-REGIONS-1]], ''::nth-fragment()'', a hypothetical selector for individual columns of a multicol…),
and the guarantees that layout containment is intended to offer would not be realized
if such mechanisms did not abide by this rule.
[[CSS-REGIONS-1]] has details over how layout containment affects
regions.
In this [[CSS-REGIONS-1]] example,
content can flow from #a to #b,
from #b to #c.
However as #c is the last fragment container in the first [=layout containment box=]
it traps all the remaining content,
and nothing gets flowed into #d, #e, or #f.
3. If the computed value of the 'overflow' property is
either ''overflow/visible'' or ''overflow/clip'' or a combination thereof,
any overflow must be treated as [=ink overflow=].
contain-layout-ink-overflow-013.html
contain-layout-ink-overflow-014.html
contain-layout-ink-overflow-015.html
contain-layout-ink-overflow-016.html
contain-layout-ink-overflow-017.html
contain-layout-ink-overflow-018.html
contain-layout-ink-overflow-019.html
contain-layout-ink-overflow-020.html
contain-layout-overflow-001.html
contain-layout-overflow-002.html
4. The [=layout containment box=] establishes an [=absolute positioning containing block=] and a [=fixed positioning containing block=].
contain-layout-006.html
contain-layout-007.html
contain-layout-cell-001.html
contain-layout-cell-002.html
contain-layout-021.html
contain-layout-containing-block-absolute-001.html
contain-layout-containing-block-fixed-001.html
5. The [=layout containment box=] creates a stacking context.
contain-layout-016.html
contain-layout-017.html
contain-layout-018.html
contain-layout-stacking-context-001.html
6. [=Forced breaks=] are allowed within [=layout containment boxes=]
but do not propagate to the parent as otherwise described in [[CSS-BREAK-3#break-between]].
contain-layout-breaks-001.html
contain-layout-breaks-002.html
Note: This introduces the previously non-existent possibility that [=forced breaks=]
may occur between a box and its container (See [[CSS-BREAK-3#possible-breaks]]).
7. For the purpose of the 'vertical-align' property,
or any other property whose effects
need to relate the position of the [=layout containment box=]'s baseline
to something other than its descendants,
the [=layout containment box|containment box=] is treated as having no baseline.
contain-layout-baseline-001.html
contain-layout-flexbox-001.html
contain-layout-grid-001.html
contain-layout-baseline-002.html
contain-layout-baseline-003.html
contain-layout-baseline-004.html
contain-layout-baseline-005.html
contain-layout-suppress-baseline-001.html
contain-layout-suppress-baseline-002.html
However, giving an element [=layout containment=]
has no effect if any of the following are true:
* if the element does not generate a principal box
(as is the case with ''display: contents'' or ''display: none'')
contain-layout-ignored-cases-no-principal-box-001.html
contain-layout-ignored-cases-no-principal-box-002.html
contain-layout-ignored-cases-no-principal-box-003.html
* if its [=principal box=] is
an internal table box
other than ''display/table-cell''
contain-layout-009.html
contain-layout-010.html
contain-layout-011.html
contain-layout-012.html
contain-layout-013.html
contain-layout-014.html
* if its [=principal box=] is
an internal ruby box
or a non-atomicinline-level box
contain-layout-002.html
contain-layout-003.html
contain-layout-004.html
contain-layout-005.html
contain-layout-001.html
contain-layout-independent-formatting-context-003.html
contain-layout-ignored-cases-ib-split-001.html
Possible Layout-Containment Optimizations
This section is non-normative.
Possible optimizations that can be enabled by layout containment include (but are not limited to):
1. When laying out the page,
the contents of separate [=layout containment boxes|containment boxes=]
can be laid out in parallel,
as they're guaranteed not to affect each other.
2. When laying out the page,
if the [=layout containment box|containment box=] is off-screen or obscured
and the layout of the visible parts of the screen do not depend on the size of the [=layout containment box|containment box=]
(for example, if the [=layout containment box|containment box=] is near the end of a block container,
and you're viewing the beginning of the block container),
the layout of the [=layout containment box|containment box=]' contents can be delayed or done at a lower priority.
(When paired with size containment,
this optimization can be applied more liberally.)
Style Containment
Giving an element style containment
has the following effects:
1. The 'counter-increment' and 'counter-set' properties
must be scoped to the element's sub-tree
and create a new counter.
contain-style-counters-001.html
contain-style-counters-002.html
contain-style-counters-003.html
contain-style-counters-004.html
contain-style-ol-ordinal-li-container.html
contain-style-ol-ordinal-pseudo-reversed.html
contain-style-ol-ordinal-pseudo.html
contain-style-ol-ordinal-reversed.html
contain-style-ol-ordinal-start-reversed.html
contain-style-ol-ordinal-start.html
contain-style-ol-ordinal.html
2. The effects of the 'content' property's
''content/open-quote'', ''content/close-quote'', ''content/no-open-quote'' and ''content/no-close-quote''
must be scoped to the element's sub-tree.
Note: This implies that the depth of quote nesting in the subtree
is unchanged and starts at the value that its context normally implies,
but that changes to the depth of quote nesting by these values inside the subtree
do not affect the depth of quote nesting outside the subtree.
quote-scoping-001.html
quote-scoping-002.html
quote-scoping-003.html
quote-scoping-004.html
quote-scoping-empty-style-boundaries.html
quote-scoping-invalidation-001.html
quote-scoping-invalidation-002.html
quote-scoping-invalidation-003.html
quote-scoping-invalidation-004.html
contain-style-baseline-001.html
contain-style-breaks-001.html
contain-style-breaks-002.html
contain-style-breaks-003.html
contain-style-breaks-004.html
contain-style-breaks-005.html
However, giving an element [=style containment=]
has no effect if any of the following are true:
* if the element does not generate a principal box
(as is the case with ''display: contents'' or ''display: none'')
Note: [[CSS-REGIONS-1]] has normative requirements on how style containment affects regions.
A scoped property has its effects scoped to a particular element or subtree.
* If scoped to an element,
it must act as if the scoping element was the root of the document
for the purpose of evaluating the property's effects:
any uses of the property outside the scoping element must have no effect on the uses of the property on or in the scoping element,
and vice versa.
Note: “Scoping to an element” is currently unused.
It is defined as an extension point for future specifications to use.
* If scoped to a sub-tree, it's the same,
except the scoping element itself is counted as "outside" the tree,
like the rest of the document,
and the effects of the property on that element are unaffected by scoping.
When considering the effects of the scoped property on elements inside the subtree,
the element at the base of the subtree is treated as if it was the root of the document.
counter-scoping-001.html
counter-scoping-002.html
counter-scoping-003.html
counter-scoping-004.html
contain-style-ol-ordinal-li-container.html
contain-style-ol-ordinal-pseudo-reversed.html
contain-style-ol-ordinal-pseudo.html
contain-style-ol-ordinal-reversed.html
contain-style-ol-ordinal-start-reversed.html
contain-style-ol-ordinal-start.html
contain-style-ol-ordinal.html
As 'counter-increment' is scoped to an element's subtree,
the first use of it within the subtree
creates a fresh counter,
regardless of whether the counter had been used outside the scoping element.
Any increments made within the subtree have no effect on counters of the same name outside the scoping element.
However, the ''content/counter()'' and ''content/counters()'' value of the 'content' property is not itself scoped,
and can refer to counters established outside of the subtree.
For example, the following markup and style:
body {
counter-reset: foo;
}
div {
counter-increment: foo;
/* and to help observe nesting properly */
margin: .2em;
padding: .2em;
background: #0001;
}
div::before {
content: counters(foo, ".");
}
Will render like:
1
2
2.1
2.2
3
4
5
Here, the style-contained element still interacts with the ''foo'' counter normally,
incrementing it to 2.
Its ''::before'' pseudo-element,
which is effectively a child and thus within the containment boundary,
can still see that counter normally,
and thus will render the string "2".
Later siblings of the style-contained element don't see anything that goes on within the boundary,
so they increment the ''foo'' counter to 3 and beyond.
Within the containment, however,
the descendant divs aren't allowed to modify the value of the outside counter,
so instead they'll create a fresh (nested) ''foo'' counter
when they attempt to increment it.
Possible Style-Containment Optimizations
This section is non-normative.
Possible optimizations that can be enabled by style containment include (but are not limited to):
1. Whenever a property is changed on a descendant of an element with [=style containment=],
calculating what part of the DOM tree is "dirtied" and might need to have its style recalculated
can stop at the element with [=style containment=].
Paint Containment
Giving an element paint containment
makes its [=principal box=] a paint containment box
and has the following effects:
1. The contents of the element
including any [=ink overflow|ink=] or [=scrollable overflow=]
must be clipped to the overflow clip edge of the [=paint containment box=],
taking [[css-backgrounds-3#corner-clipping|corner clipping]] into account.
This does not include the creation of any mechanism
to access or indicate the presence of the clipped content;
nor does it inhibit the creation of any such mechanism through other properties,
such as 'overflow', 'resize', or 'text-overflow'.
contain-paint-050.html
Note: This clipping shape respects 'overflow-clip-margin',
allowing an element with [=paint containment=]
to still slightly overflow its normal bounds.
Note: The behavior is described in this paragraph is equivalent to changing
''overflow-x: visible'' into ''overflow-x: clip''
and
''overflow-y: visible'' into ''overflow-y: clip''
at used value time,
while leaving other values of 'overflow-x' and 'overflow-y' unchanged.
contain-paint-001.html
contain-paint-004.html
contain-paint-047.html
contain-paint-048.html
contain-paint-cell-001.html
contain-paint-cell-002.html
contain-paint-clip-011.html
contain-paint-clip-012.html
contain-paint-clip-013.html
contain-paint-clip-014.html
contain-paint-clip-015.html
contain-paint-clip-016.html
contain-paint-clip-017.html
contain-paint-clip-018.html
contain-paint-clip-019.html
contain-paint-table-001.html
contain-paint-table-002.html
contain-paint-026.html
contain-paint-049.html
contain-paint-clip-001.html
contain-paint-clip-002.html
contain-paint-clip-003.html
contain-paint-clip-004.html
contain-paint-clip-005.html
contain-paint-clip-006.html
2. The [=paint containment box=] establishes an [=absolute positioning containing block=] and a [=fixed positioning containing block=].
contain-paint-009.html
contain-paint-010.html
contain-paint-022.html
contain-paint-023.html
contain-paint-024.html
contain-paint-containing-block-absolute-001.html
contain-paint-containing-block-fixed-001.html
3. The [=paint containment box=] creates a stacking context.
contain-paint-020.html
contain-paint-021.html
contain-paint-025.html
contain-subgrid-001.html
contain-paint-stacking-context-001a.html
contain-paint-stacking-context-001b.html
4. The [=paint containment box=] [=establishes an independent formatting context=].
contain-paint-ifc-011.html
contain-paint-independent-formatting-context-001.html
contain-paint-independent-formatting-context-002.html
contain-paint-formatting-context-float-001.html
contain-paint-formatting-context-margin-001.html
contain-paint-baseline-001.html
However, giving an element [=paint containment=]
has no effect if any of the following are true:
* if the element does not generate a principal box
(as is the case with ''display: contents'' or ''display: none'')
contain-paint-ignored-cases-no-principal-box-001.html
* if its [=principal box=] is
an internal table box
other than ''display/table-cell''
contain-paint-014.html
contain-paint-015.html
contain-paint-016.html
contain-paint-017.html
contain-paint-018.html
contain-paint-019.html
contain-paint-ignored-cases-internal-table-001a.html
contain-paint-ignored-cases-internal-table-001b.html
* if its [=principal box=] is
an internal ruby box
or a non-atomicinline-level box
contain-paint-005.html
contain-paint-006.html
contain-paint-007.html
contain-paint-008.html
contain-paint-ignored-cases-ruby-containing-block-001.html
contain-paint-ignored-cases-ruby-stacking-and-clipping-001.html
contain-paint-002.html
contain-paint-011.html
contain-paint-012.html
contain-paint-independent-formatting-context-003.html
contain-paint-ignored-cases-ib-split-001.html
Possible Paint-Containment Optimizations
This section is non-normative.
Possible optimizations that can be enabled by paint containment include (but are not limited to):
1. If the [=paint containment box|containment box=] is off-screen or obscured,
the UA can usually skip trying to paint its contents,
as they're guaranteed to be off-screen/obscured as well.
Note: Some paint effects such as the ''blur()'' filter from [[FILTER-EFFECTS-1]]
have non local effects.
The user agent needs to keep track of these,
as it may need to repaint parts of an element with such a filter
when its descendents change,
even if they have [=paint containment=]
and could otherwise be skipped.
2. Unless the clipped content is made accessible via a separate mechanism
such as the 'overflow', 'resize', or 'text-overflow' properties,
the UA can reserve "canvas" space for the box exactly the box's size.
(In similar, scrollable, situations, like ''overflow: hidden'',
it's possible to scroll to the currently-clipped content,
so UAs often predictively overpaint somewhat
so there's something to see as soon as the scroll happens,
rather than a frame later.)
3. Because they are guaranteed to be stacking contexts,
scrolling elements can be painted into a single GPU layer.
Suppressing An Element's Contents Entirely: the 'content-visibility' property {#content-visibility}
=================
content-visibility/content-visibility-085.html
content-visibility/content-visibility-086.html
content-visibility/content-visibility-087.html
content-visibility/content-visibility-088.html
content-visibility/content-visibility-089.html
content-visibility/content-visibility-090.html
content-visibility/content-visibility-091.html
content-visibility/content-visibility-092.html
content-visibility/content-visibility-093.html
content-visibility/content-visibility-094.html
content-visibility/content-visibility-095.html
content-visibility/content-visibility-096.html
content-visibility/content-visibility-097.html
content-visibility/content-visibility-098.html
content-visibility/content-visibility-099.html
content-visibility/content-visibility-animation-and-scroll.html
content-visibility/content-visibility-animation-becomes-visible.html
content-visibility/content-visibility-animation-in-auto-subtree.html
content-visibility/content-visibility-animation-with-scroll-timeline-in-auto-subtree.html
content-visibility/content-visibility-animation-with-scroll-timeline-in-hidden-subtree.html
content-visibility/content-visibility-auto-applied-to-th-crash.html
content-visibility/content-visibility-auto-first-observation-immediate.html
content-visibility/content-visibility-auto-nested-scroll.html
content-visibility/content-visibility-auto-nested.html
content-visibility/content-visibility-auto-relevancy-updates.html
content-visibility/content-visibility-auto-text-fragment.html
content-visibility/content-visibility-background-clip-crash.html
content-visibility/content-visibility-interpolation.html
content-visibility/content-visibility-intrinsic-size-001.html
content-visibility/content-visibility-layout-containment-001.html
content-visibility/content-visibility-layout-paint-containment-001.html
content-visibility/content-visibility-on-g.html
content-visibility/content-visibility-on-root-svg.html
content-visibility/content-visibility-paint-containment-001.html
content-visibility/content-visibility-paint-containment-002.html
content-visibility/content-visibility-paint-containment-003.html
content-visibility/content-visibility-selection-crash.html
content-visibility/content-visibility-size-containment-001.html
content-visibility/content-visibility-style-containment-001.html
content-visibility/content-visibility-svg-path.html
content-visibility/content-visibility-svg-rect.html
content-visibility/content-visibility-svg-text.html
content-visibility/content-visibility-vs-scrollIntoView-001.html
content-visibility/content-visibility-vs-scrollIntoView-002.html
content-visibility/content-visibility-vs-scrollIntoView-003.html
content-visibility/content-visibility-web-animation-in-auto-subtree.html
content-visibility/content-visibility-with-float-crash.html
content-visibility/content-visibility-with-popover-top-layer-000.html
content-visibility/content-visibility-with-popover-top-layer-001.html
content-visibility/content-visibility-with-popover-top-layer-002.html
content-visibility/content-visibility-with-popover-top-layer-003.html
content-visibility/content-visibility-with-popover-top-layer-004.html
content-visibility/content-visibility-with-popover-top-layer-005.html
content-visibility/content-visibility-with-popover-top-layer-006.html
content-visibility/content-visibility-with-popover-top-layer-and-auto-descendant.html
content-visibility/content-visibility-with-popover-top-layer-hide-after-addition.html
content-visibility/content-visibility-with-top-layer-007.html
content-visibility/content-visibility-with-top-layer-008.html
content-visibility/content-visibility-with-top-layer-and-auto-descendant.html
content-visibility/content-visibility-with-top-layer-in-auto-subtree-removal.html
Name: content-visibility
Value: visible | auto | hidden
Initial: visible
Inherited: no
Applies to: elements for which [=size containment=] can apply
Animation type: see [[#content-visibility-animation]]
content-visibility/content-visibility-051.html
content-visibility/content-visibility-073.html
content-visibility/inheritance.html
content-visibility/parsing/content-visibility-computed.html
content-visibility/parsing/content-visibility-invalid.html
content-visibility/parsing/content-visibility-valid.html
content-visibility/content-visibility-077.html
content-visibility/content-visibility-resize-observer-no-error.html
content-visibility/content-visibility-069.html
content-visibility/content-visibility-auto-selection-crash.html
content-visibility/content-visibility-continuations-crash.html
content-visibility/content-visibility-form-controls-crash.html
content-visibility/content-visibility-hit-test-contents-crash.html
content-visibility/content-visibility-in-svg-000-crash.html
content-visibility/content-visibility-output-crash.html
content-visibility/contentvisibility-nestedslot-crash.html
content-visibility/crashtests/first-line-and-inline-block.html
content-visibility/detach-locked-slot-children-crash.html
content-visibility/hidden-execcommand-crash.html
content-visibility/hidden-pseudo-element-removed-crash.html
content-visibility/meter-selection-crash.html
content-visibility/slot-content-visibility-1-crash.html
content-visibility/slot-content-visibility-10-crash.html
content-visibility/slot-content-visibility-11-crash.html
content-visibility/slot-content-visibility-12-crash.html
content-visibility/slot-content-visibility-13-crash.html
content-visibility/slot-content-visibility-14-crash.html
content-visibility/slot-content-visibility-15-crash.html
content-visibility/slot-content-visibility-16-crash.html
content-visibility/slot-content-visibility-17-crash.html
content-visibility/slot-content-visibility-18-crash.html
content-visibility/slot-content-visibility-19-crash.html
content-visibility/slot-content-visibility-2-crash.html
content-visibility/slot-content-visibility-20-crash.html
content-visibility/slot-content-visibility-21-crash.html
content-visibility/slot-content-visibility-22-crash.html
content-visibility/slot-content-visibility-3-crash.html
content-visibility/slot-content-visibility-4-crash.html
content-visibility/slot-content-visibility-5-crash.html
content-visibility/slot-content-visibility-6-crash.html
content-visibility/slot-content-visibility-7-crash.html
content-visibility/slot-content-visibility-8-crash.html
content-visibility/slot-content-visibility-9-crash.html
content-visibility/crashtests/content-visibility-transition-finished-001.html
content-visibility/crashtests/grid-dynamic.html
content-visibility/display-ruby-text-crash.html
content-visibility/locked-frame-crash.html
content-visibility/touch-action-beside-display-locked-fixedpos-iframe-crash.html
The 'content-visibility' property
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.
It has the following values:
: visible
::
No effect.
The element's contents are laid out and rendered as normal.
content-visibility/content-visibility-002.html
content-visibility/content-visibility-012.html
content-visibility/content-visibility-013.html
content-visibility/content-visibility-014.html
content-visibility/content-visibility-023.html
content-visibility/content-visibility-024.html
content-visibility/content-visibility-025.html
content-visibility/content-visibility-042.html
content-visibility/content-visibility-052.html
content-visibility/content-visibility-057.html
content-visibility/content-visibility-with-top-layer-003.html
: hidden
::
The element [=skips its contents=].
content-visibility/content-visibility-001.html
content-visibility/content-visibility-003.html
content-visibility/content-visibility-004.html
content-visibility/content-visibility-005.html
content-visibility/content-visibility-006.html
content-visibility/content-visibility-007.html
content-visibility/content-visibility-008.html
content-visibility/content-visibility-009.html
content-visibility/content-visibility-010.html
content-visibility/content-visibility-011.html
content-visibility/content-visibility-015.html
content-visibility/content-visibility-016.html
content-visibility/content-visibility-017.html
content-visibility/content-visibility-018.html
content-visibility/content-visibility-019.sub.https.html
content-visibility/content-visibility-020.html
content-visibility/content-visibility-021.html
content-visibility/content-visibility-022.html
content-visibility/content-visibility-026.html
content-visibility/content-visibility-028.html
content-visibility/content-visibility-029.html
content-visibility/content-visibility-030.html
content-visibility/content-visibility-031.html
content-visibility/content-visibility-032.html
content-visibility/content-visibility-033.sub.https.html
content-visibility/content-visibility-034.html
content-visibility/content-visibility-036.html
content-visibility/content-visibility-037.html
content-visibility/content-visibility-038.html
content-visibility/content-visibility-039.html
content-visibility/content-visibility-040.html
content-visibility/content-visibility-041.html
content-visibility/content-visibility-043.html
content-visibility/content-visibility-044.html
content-visibility/content-visibility-045.html
content-visibility/content-visibility-072.html
content-visibility/content-visibility-078.html
content-visibility/content-visibility-082.html
content-visibility/content-visibility-canvas.html
content-visibility/content-visibility-forced-layout-client-rects.html
content-visibility/content-visibility-img.html
content-visibility/content-visibility-input-image.html
content-visibility/content-visibility-svg.html
content-visibility/content-visibility-video.html
content-visibility/content-visibility-fieldset-size.html
content-visibility/content-visibility-with-top-layer-000.html
content-visibility/content-visibility-with-top-layer-001.html
content-visibility/content-visibility-with-top-layer-002.html
content-visibility/document-element-computed-style.html
content-visibility/element-reassigned-to-skipped-slot.html
content-visibility/element-reassigned-to-slot-in-skipped-subtree.html
content-visibility/scrollIntoView-target-with-contents-hidden.html
content-visibility/scrollIntoView-with-focus-target-with-contents-hidden.html
content-visibility/content-visibility-with-top-layer-hide-after-addition.html
content-visibility/dynamic-change-paint-fully-obscuring-child-001.html
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.
content-visibility/content-visibility-035.html
content-visibility/content-visibility-047.html
content-visibility/content-visibility-056.html
content-visibility/content-visibility-060.html
content-visibility/content-visibility-061.html
content-visibility/content-visibility-067.html
content-visibility/content-visibility-083.html
content-visibility/content-visibility-084.html
Note: This is similar to giving the contents ''display: none''.
content-visibility/content-visibility-041.html
: auto
::
Changes the [=used value=] of the 'contain' property
so as to turn on [=layout containment=],
[=style containment=],
and [=paint containment=] for the element.
content-visibility/content-visibility-026.html
content-visibility/content-visibility-027.html
content-visibility/content-visibility-074.html
content-visibility/content-visibility-auto-in-iframe.html
content-visibility/content-visibility-auto-intrinsic-width.html
content-visibility/content-visibility-auto-state-changed-first-observation.html
content-visibility/content-visibility-auto-state-changed-removed.html
content-visibility/content-visibility-auto-state-changed.html
content-visibility/content-visibility-with-top-layer-005.html
content-visibility/content-visibility-with-top-layer-006.html
If the element is not [=relevant to the user=],
it also [=skips its contents=].
content-visibility/content-visibility-046.html
content-visibility/content-visibility-050.html
content-visibility/content-visibility-058.html
content-visibility/content-visibility-064.html
content-visibility/content-visibility-068.html
content-visibility/content-visibility-072.html
content-visibility/content-visibility-079.html
content-visibility/content-visibility-with-top-layer-003.html
content-visibility/content-visibility-auto-state-changed-first-observation.html
content-visibility/content-visibility-auto-state-changed.html
Unlike ''content-visibility/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.
content-visibility/content-visibility-048.html
content-visibility/content-visibility-049.html
content-visibility/content-visibility-050.html
content-visibility/content-visibility-053.html
content-visibility/content-visibility-054.html
content-visibility/content-visibility-055.html
content-visibility/content-visibility-058.html
content-visibility/content-visibility-062.html
content-visibility/content-visibility-063.html
content-visibility/content-visibility-064.html
content-visibility/content-visibility-065.html
content-visibility/content-visibility-066.html
content-visibility/content-visibility-068.html
content-visibility/content-visibility-070.html
content-visibility/content-visibility-071.html
content-visibility/content-visibility-075.html
content-visibility/content-visibility-076.html
When an element skips its contents,
the user agent must change the [=used value=] of the 'contain' property
so as to turn on [=layout containment=],
[=style containment=],
[=paint containment=],
and [=size containment=].
Further, its contents
(the [=flat tree=] descendants of the element,
including both text and elements,
or the replaced content of a [=replaced element=])
are not painted
(as if they had ''visibility: hidden'')
and do not respond to hit-testing
(as if they had ''pointer-events: none''),
and to a large extent do not update their styles at all
unless explicitly requested by script
(see [[#cv-notes]] for details).
content-visibility/content-visibility-001.html
content-visibility/content-visibility-003.html
content-visibility/content-visibility-004.html
content-visibility/content-visibility-005.html
content-visibility/content-visibility-006.html
content-visibility/content-visibility-007.html
content-visibility/content-visibility-008.html
content-visibility/content-visibility-009.html
content-visibility/content-visibility-010.html
content-visibility/content-visibility-011.html
content-visibility/content-visibility-015.html
content-visibility/content-visibility-016.html
content-visibility/content-visibility-017.html
content-visibility/content-visibility-018.html
content-visibility/content-visibility-020.html
content-visibility/content-visibility-021.html
content-visibility/content-visibility-022.html
content-visibility/content-visibility-026.html
content-visibility/content-visibility-028.html
content-visibility/content-visibility-034.html
content-visibility/content-visibility-035.html
content-visibility/content-visibility-036.html
content-visibility/content-visibility-037.html
content-visibility/content-visibility-038.html
content-visibility/content-visibility-039.html
content-visibility/content-visibility-040.html
content-visibility/content-visibility-041.html
content-visibility/content-visibility-045.html
content-visibility/content-visibility-051.html
content-visibility/content-visibility-072.html
content-visibility/content-visibility-078.html
content-visibility/content-visibility-080.html
content-visibility/content-visibility-canvas.html
content-visibility/content-visibility-fieldset-size.html
content-visibility/content-visibility-forced-layout-client-rects.html
content-visibility/content-visibility-img.html
content-visibility/content-visibility-input-image.html
content-visibility/content-visibility-svg.html
content-visibility/content-visibility-video.html
content-visibility/content-visibility-with-top-layer-hide-after-addition.html
content-visibility/document-element-computed-style.html
content-visibility/element-reassigned-to-skipped-slot.html
content-visibility/element-reassigned-to-slot-in-skipped-subtree.html
content-visibility/content-visibility-auto-state-changed-first-observation.html
The user agent should additionally avoid as much layout/rendering work as possible
for [=skipped contents=];
the combination of heavy [=containment=]
and making the contents invisible and untouchable
enables heavy optimizations.
If rendering work is done at some point,
the user-agent should retain the previously computed layout state if possible,
to allow the [=skipped contents=] to be displayed quickly at a later moment.
content-visibility/content-visibility-081.html
If an element has a value other than ''content-visibility: visible'',
then the following properties hold:
* [=layout containment=] ensures that
the user-agent is able to omit layout work in skipped subtrees,
since the results of such layouts will not affect elements outside of the container element.
* [=style containment=] ensures that
counters do not have to be processed in skipped subtrees,
since they do not affect counters outside of the container element.
* [=paint containment=] ensures that
ink overflow of painted contents is clipped;
this, in turn, means that user-agent can reliably determine
when the visible portion of the element approaches the viewport
(and, for ''content-visibility: auto'', start painting it).
* [=size containment=] ensures that
the user-agent is able to omit layout in skipped subtrees,
since the results of such layouts
will not affect the container element’s size.
Note that in the ''content-visibility: auto'' case,
[=layout containment=], [=style containment=], and [=paint containment=] persist even if the element is not [=skipped=].
This is done to prevent layout changes that would be incurred by [=containment=] changes
as a result of an element entering and exiting the [=skipped=] state.
An element that has ''content-visibility: auto'' is in one of three states
when it comes to its proximity to the viewport:
* The element is close to the viewport:
In this state, the element is considered "on-screen":
its [=paint containment box=]'s [=overflow clip edge=] intersects with the viewport,
or a user-agent defined margin around the viewport.
Note: This margin is meant to allow the user agent
to begin preparing for an element to be in the viewport soon.
A margin of 50% is suggested as a reasonable default.
If a filter (see [[FILTER-EFFECTS-1]]) with non local effects includes the element as part of its input,
the user agent should also treat the element as relevant to the user
when the filter's output can affect the rendering within the viewport
(or within the user-agent defined margin around the viewport),
even if the element itself is still off-screen.
* The element is far away from the viewport:
In this state, the element's proximity to the viewport has been computed and is not [=close to the viewport=].
* The element's [=proximity to the viewport=] is not determined:
In this state, the computation to determine the element's [=proximity to the viewport=] has not been done
since the last time the element was connected.
Initially, the element's [=proximity to the viewport=] is [=not determined=].
Only connected elements with ''content-visibility: auto'' determine their [=proximity to the viewport=].
When the element becomes disconnected, the element's [=proximity to the viewport=] becomes [=not determined=].
An element is relevant to the user
if any of the following conditions are true:
* The element is [=close to the viewport=].
content-visibility/content-visibility-046.html
content-visibility/content-visibility-079.html
content-visibility/content-visibility-auto-in-iframe.html
content-visibility/content-visibility-auto-intrinsic-width.html
* Either the element or its [=contents=]
are focused,
as described in the focus section of the HTML spec.
content-visibility/content-visibility-050.html
content-visibility/content-visibility-064.html
content-visibility/content-visibility-068.html
* Either the element or its [=contents=]
are selected,
where selection is described in the selection API.
content-visibility/content-visibility-070.html
content-visibility/content-visibility-071.html
* Either the element or its [=contents=]
are placed in the [=top layer=].
content-visibility/content-visibility-with-top-layer-004.html
content-visibility/content-visibility-with-top-layer-005.html
content-visibility/content-visibility-with-top-layer-006.html
* The element has a [=flat tree=] descendant that is [=captured in a view transition=].
Animating and Interpolating 'content-visibility'
In general,
the 'content-visibility' property’s [=animation type=] is [=discrete=].
However,
similar to interpolation of 'visibility'
(see [[web-animations-1#animating-visibility]]),
during interpolation between ''content-visibility/hidden''
and any other 'content-visibility' value,
p values between 0 and 1
map to the non-''content-visibility/hidden'' value.
Using ''content-visibility: hidden''
This section is non-normative.
''content-visibility: hidden'' lays powerful restrictions onto an element,
and so should be used with caution.
It also enables some very useful scenarios,
often improving on existing techniques,
a few of which are outlined here.
1. If a page needs to take some measurements of elements or text
which aren't themselves going to be rendered,
commonly this is done by positioning the stuff-to-be-measured off-screen,
using something like ''position: absolute; left: -100000px;'',
then calling an API like {{Element/getBoundingClientRect()}}.
Unfortunately, even though the page never intends to display this content,
the user agent will still have to do full styling, layout, and rendering for the content,
just in case it affects what's shown on screen.
The author also can't,
without further work,
guarantee that the content won't accidentally show up on-screen;
even a very negative 'left' value (like above) might not be enough,
depending on the content.
Wrapping this content in a ''content-visibility: hidden'' container
solves all of these problems.
If the wrapper has no border, background, etc,
then it and its [=skipped contents=] are guaranteed to never render anything to the screen,
no matter how big they get.
Because the contents are [=skipped contents|skipped=],
the user agent can also avoid styling or laying them out
until absolutely necessary,
when script finally asks for it.
2. A "single-page app" often consists of several independent panes or "views",
of which only one is displayed at a time.
If the author wants to avoid paying styling/layout/rendering/etc cost
for the inactive views,
they can remove them from the document entirely,
or at minimum apply ''display:none'' to them.
Unfortunately,
this means that when the view does need to be displayed,
all of the styling/layout/rendering/etc work needs to be done all at once,
potentially causing a noticeable delay before the view actually shows up.
Alternately, the view can just be positioned off-screen.
This means it'll be immediately ready when it's time to be used,
but it incurs the cost of styling/layout/rendering all the time,
which might be significant,
especially if there are a number of inactive views.
The inactive views also might still show up to accessibility tooling,
confusing users of screen-readers,
people using Ctrl-F to find-in-page, etc.
''content-visibility: hidden'' improves on both of these options.
Because the contents are [=skipped=],
the user agent isn't spending time on them when they're not active.
They're also not visible to screen readers,
find-in-page,
and other tools.
And because user agents should preserve previous styling/layout work if possible,
if the view was displayed before,
re-rendering it might be very fast.
3. If an author wants to make an element "invisible",
but still show up in the page for layout purposes,
one option is ''visibility: hidden''.
However, descendants of a ''visibility: hidden'' element
can set ''visibility: visible''
and start showing up again,
which isn't always intuitive or expected.
''content-visibility: hidden'' performs a very similar purpose,
but descendants can't turn it "off" and start displaying;
they stay "hidden" until the ancestor turns it off.
Because ''content-visibility: hidden'' also applies many [=containment=] values to the container,
it's not always quite as usable as ''visibility: hidden'' would be,
but when its restrictions are acceptable,
it can be a more reliable,
more consistent way to hide an element's contents.
Using ''content-visibility: auto''
This section is non-normative.
''content-visibility: auto'' is a more complex value than ''content-visibility/hidden'';
rather than being similar to ''display: none'',
it adaptively hides/displays an element's contents
as they become [=relevant to the user=].
It also doesn't hide its [=skipped contents=] from the user agent,
so screen readers,
find-in-page,
and other tools can still interact with it.
It is best to think of it as
an upgrade to [=containment=]:
if an author has a large amount of content to display
that will often be off-screen
(such as a long scrollable list),
and that content is okay with heavy [=containment=],
they should consider using ''content-visibility: auto''
to apply all of the [=containments=] at once.
This also strongly hints to the user agent
that it's acceptable to skip work on the contents
(possibly causing a small delay when they do come on-screen)
because it's more important to have a large amount of content in the document
and most of it won't be seen anyway.
Note: ''content-visibility: auto'' can thus be used
instead of complicated "virtual list" techniques,
at least in many cases.
Because ''content-visibility: auto'' only causes the element to [=skip=] its contents
when none of it is [=relevant to the user=],
it's best to use at a reasonably fine granularity.
For example, on Twitter,
applying ''content-visibility: auto'' to the entire timeline
wouldn't accomplish much--
it's always on-screen,
and so it will never [=skip its contents=].
Instead, 'content-visibility' should be applied to individual tweets,
allowing each of them to be [=skipped=]
as they go off-screen.
Because ''content-visibility: auto'' imposes [=size containment=]
when the element [=skips its contents=],
if the element depends on its contents to determine its size
the layout of the page
(or at least, the scrollbar position)
can "jump around" as elements go off-screen and start [=skipping=].
This can be fixed in a number of ways:
* making the element fixed-size
* carefully arranging a layout such as Grid
to size the element without depending on its contents
* using 'contain-intrinsic-size' to set an estimate of the element's size
* using ''contain-intrinsic-size: auto'' to automatically "snapshot" the exact size of the element
from the last time it was rendered,
before it was [=skipped=]
(along with providing an estimate of the size
to be used before it's rendered and can have its size snapshotted)
For example,
on Twitter,
the average tweet is approximately 200px tall,
so ''contain-intrinsic-size: auto 500px 200px''
will ensure that the scrollbar thumb is in approximately the correct size and position
even when preceding or following tweets are [=skipped=],
while still allowing the tweets to size according to their contents
when they're on-screen.
As long as the tweets have all been viewed at least once
(and haven't changed size while they were [=skipped=]),
their sizes will be exactly correct while they're [=skipped=],
so the scrollbar thumb will be as well;
only freshly-loaded tweets
(such as those loaded at the top of the timeline
while you are scrolling further down)
will be forced to rely on the ''200px'' height estimate.
Detecting ''content-visibility: auto'' state changes: the contentvisibilityautostatechange event {#content-visibility-auto-state-change}
--------------------------------------------------------------------------------------------------------------------------------------------
The contentvisibilityautostatechange event is fired on an element with ''content-visibility: auto'' style when
the rendering state changes and the element either becomes or stops being
[=relevant to the user=].
content-visibility/content-visibility-auto-state-changed.html
content-visibility/content-visibility-auto-state-changed-first-observation.html
content-visibility/content-visibility-auto-state-changed-removed.html
content-visibility/content-visibility-auto-state-changed.html
This event is dispatched by posting a task at the time when the state change occurs.
Description of ContentVisibilityAutoStateChangeEvent attributes:
: skipped
:: Set to true if target changed state to [=skip its contents=], and false otherwise.
content-visibility/content-visibility-auto-state-changed-first-observation.html
content-visibility/content-visibility-auto-state-changed.html
Description of ContentVisibilityAutoStateChangeEventInit members:
: skipped
:: See the description of the {{ContentVisibilityAutoStateChangeEvent/skipped}} attribute.
Note that elements in ''content-visibility: auto'' subtrees remain semantically
relevant even for elements that [=skip its contents=]. This means that it is
inappropriate to use this signal to indefinitely skip DOM updates in the
subtree that is skipped. Instead, it should be used to deprioritize updates,
but ensure that the content remains semantically relevant and reasonably
up-to-date. This is particularly important for assistive technologies which
consume this content even when the ancestor is set to [=skip its contents=].
Restrictions and Clarifications {#cv-notes}
-------------------------------------------
1. From the perspective of an {{IntersectionObserver}},
the [=skipped contents=] of an element
are never intersecting the [=intersection root=].
This is true even if both the root and the target elements
are in the [=skipped contents=].
content-visibility/content-visibility-030.html
2. From the perspective of a {{ResizeObserver}},
the [=skipped contents=] of an element
never change their size.
If these elements become non-skipped later,
the resize observation will be delivered
if the new size differs from the last size used to notify the resize observer.
content-visibility/content-visibility-031.html
3. If an element starts or stops [=skipped contents|skipping its contents=],
this change happens
after the requestAnimationFrame callbacks
of the frame that renders the effects of the change
have run.
Specifically, such changes will take effect between steps 13 and 14
of [=update the rendering=] step of the Processing Model
(between “run the animation frame callbacks”
and “run the update intersection observations steps”).
Determining the viewport intersection of the element
can be done with an internal version of an IntersectionObserver.
However, since the observations from this are dispatched at
step 14 of [=update the rendering=],
any changes to the [=skipped contents|skipped=] (and thus painted) state
will not be visible to the user until the next frame's processing.
For this reason, updating the [=skipped contents|skipped=] state,
including containment adjustments,
is deferred to that frame as well.
This ensures that script accessing,
for example,
the containment value of the element between these two events
(internal intersection observation and [=skipped contents|skipped=] state update)
will retrieve values consistent with current painted state
and not cause any forced layouts.
4. Elements with ''content-visibility: auto''
that have not determined [=proximity to the viewport=]
must determine their proximity to the viewport
in the next [=update the rendering=] cycle.
The effect of this determination must be reflected in the visual update which results from this [=update the rendering=] cycle.
See the event loop process model for the concrete algorithm description.
When an element first gains ''content-visibility: auto'', it may or may not
be positioned on screen. The determination of this state and thus
determination of whether this element is [=skipped=] must happen in the
same frame. If it does not, then there is a possibility of producing blank
content in the element's place since visibility check and [=skipped=] state
update would be deferred to the next frame.
5. For the purposes of scrolling operations,
such as {{Element/scrollIntoView()}},
an element with ''content-visibility: auto''
that is [=skipping its contents=]
has its size and location determined
with [=size containment=] still active.
content-visibility/content-visibility-058.html
Note: Once it's scrolled into view,
the element will no longer [=skip its contents=],
and so might not have [=size containment=];
if this changes the element's size,
it might not align in the viewport exactly as requested.
If an element is not available to user-agent features
(for example, if it is [=skipped=]
due to a ''content-visibility: hidden'' ancestor),
then scrolling operations
must not scroll to it at all,
as if it did not have a layout box.
content-visibility/content-visibility-043.html
content-visibility/content-visibility-056.html
6. If an element with ''content-visibility: auto''
that is [=skipping its contents=]
is focused
(or its contents are),
it becomes [=relevant to the user=]
(and thus stops [=skipping its contents=])
before it is scrolled into view due to the focusing.
content-visibility/content-visibility-064.html
Note: Thus, unlike the previous point,
the element will be correctly sized and aligned in the viewport.
This is consistent with the order of the steps for the {{Window/focus()}} method.
7. If an <{iframe}> [=skips its contents=]
or is part of an element's [=skipped contents=],
the user agent should entirely skip the [=Update The Rendering=]
step in the iframe's event loop,
if possible.
content-visibility/content-visibility-004.html
content-visibility/content-visibility-020.html
Note: At the moment the <{iframe}> starts being [=skipped=],
it needs to run that step at least once
to remove the painted output.
8. [=Skipped contents=] do not contribute to the result of {{HTMLElement/innerText}}.
content-visibility/content-visibility-029.html
9. While an element is [=skipped=],
CSS transitions and animations on the element do not update:
* New animations are not created even if newly-applied style would start one.
* Existing animations do not advance in their timeline.
* Running animations on the element do not end.
If script queries the style of a [=skipped=] element
(causing a [=style change event=])
such that knowing the state of animations or transitions is required
to return correct information,
animation and transitions are sampled
according to the styles at the time of that [=style change event=]:
content-visibility/animation-display-lock.html
[[css-animations-2#events]] and [[css-transitions-2#transition-events]]
defines what objects are created
and what events are fired,
with what data,
when an animation or transition is updated,.
When an element stops being [=skipped=],
animations and transitions are sampled
and then resume advancing on their timelines as normal from that point.
Note: Overall, this is similar to the behavior of transitions/animations
when a background tab is brought back to the foreground,
allowing user agents to skip as much unnecessary animation work as possible
without overly disrupting the animations when they become relevant again.
10. While an element is [=skipped=],
it must not start any transitions,
even if a [=style change event=] affects its computed styles.
When an element stops being [=skipped=],
it must not start any transitions
as a result of the [=style change event=]
associated with it no longer being [=skipped=].
Note: This is similar to an element switching from ''display:none''
to a non-''display/none'' value--
even though the styles are technically changing in that case
(from their initial values
to their "proper" values from the cascade),
no transitions are started.
11. If an element has an ancestor with ''content-visibility: hidden'',
and it is placed in the [=top layer=],
it does not generate any boxes,
as if it were ''display: none''.
content-visibility/content-visibility-with-top-layer-000.html
content-visibility/content-visibility-with-top-layer-001.html
content-visibility/content-visibility-with-top-layer-002.html
Note: An element [=skipped=] for other reasons,
such as having a ''content-visibility: auto'' ancestor,
will still generate boxes as normal,
and might thus become un-[=skipped=].
Accessibility Implications {#cv-a11y}
-------------------------------------
If a user agent exposes some form of "accessibility tree",
akin to the DOM tree but specialized for accessibility use-cases such as screen-readers
(thus providing the positions/etc of elements relevant to accessibility APIs,
such as focusable elements),
then the [=skipped contents=] of ''content-visibility: hidden'' elements
must similarly be "skipped" (omitted) in the accessibility tree
(similar to how ''display: none'' elements
are omitted in all views of the document).
[=Skipped contents=] of ''content-visibility: auto'' elements
must not expose the fact that a user is interacting with the page via the accessibility tree,
rather than via rendering visually to the screen.
In particular, if a user agent uses ''content-visibility: auto''
to avoid doing layout and painting work on off-screen content
for displaying to the screen,
it must similarly avoid doing that work on off-screen content
for representing in the accessibility tree.
If this is not possible
(for example, if the user agent's representation of a focusable element in the accessibility tree
requires knowledge of its exact position,
and thus requires a full layout to be done on it and surrounding contents),
then the user agent must omit the [=skipped contents=] from the accessibility tree entirely.
Note: This requirement is intended to protect users utilizing accessibility tooling
from being identified and profiled as such
via observation of timing channels;
if a user agent can skip significant amounts of work
when rendering visually,
but has to do all of the work when rendering to an accessibility tree,
then an author can tell how a user is interacting with the page
by observing the timing of layout operations.
Examples {#cv-examples}
-----------------------
... some content goes here ...
The .sv element's ''content-visibility: auto'' value
lets the user-agent manage whether the element is [=skipped=].
Specifically when this element is near the viewport,
the user-agent will begin painting the element.
When the element moves away from the viewport,
it will stop being painted.
In addition, the user-agent should skip as much of the rendering work as possible
when the element is [=skipped=].
... some content goes here ...
In this case, the element is [=skipped=] regardless of viewport intersection.
This means that the only way to have the [=contents=] painted
is via script updating the value to remove 'content-visibility' or change its value.
As before, the user-agent should skip as much of the rendering in the [=contents=] as possible.
An additional effect of skipping rendering
is that the layout state of the [=contents=] can be preserved by the user-agent,
so that removing the 'content-visibility' property in the future
will cause the [=contents=] to be rendered quicker
than if they were hidden with ''display: none'' or similar.
... some other content goes here ...
Similarly to the last example, the element is [=skipped=].
The user-agent should avoid as much rendering work as possible.
However, in this example, at some point script accesses a layout value in the element's [=contents=].
In this situation, the user-agent cannot avoid rendering work
and has to process any previously skipped rendering work
in order to return a correct value to the caller.
In this example, the result of {{Element/getBoundingClientRect()}}
is a rect positioned at (11, 22) with a size 100x200.
Note that repeated calls to the same layout value
should not cause any additional rendering work,
since the user-agent should retain the last updated rendering state.
Also note that this situation in which rendering work is required is not unique.
There may be other situations in which the user-agent cannot avoid rendering work.
Privacy Considerations
There are no known privacy impacts of the features in this specification.
Security Considerations
There are no known security impacts of the features in this specification.
Like any other CSS specification, it affects the rendering of the document,
but does not introduce any special ability to present content in a misleading way
that was not previously available through other CSS modules
and that isn't inherent to the act of formatting the document.
* Updated relevant to the user selection to point to the selection API instead of highlight pseudos.
* Referenced the HTML event loop process model in the [[#cv-notes]], clarification 4.
* defined [=proximity to the viewport=] and used it in the [[#cv-notes]], clarification 4.
* 'content-visibility' applies to the same properties as [=size containment=] rather than [=layout containment=]
* clarified that 'content-visibility' affects the used value, not computed value, of the 'contain' property
* Updated the ContentVisibilityAutoStateChanged event name to ContentVisibilityAutoStateChange to follow the convention for event names.
* Move the definition of inline-size containement from the Level 3 specification
to this Level 2.
(Issue 10433)
* Make the 'content-visibility' property animatable.
(Issue 8627)
* Included [=style containment=] in the ''strict'' and ''content'' keywords.
* Use the [=overflow clip edge=] rather than the [=border edge=] when deciding if the element is “on screen”, as part of determining if it is [=relevant to the user=]
* Define how animations and transitions act on skipped elements
* Remove "at risk" marker from style containment
* Disable propagation from the HTML body element when containment is on
* Made style containment part of ''strict'' and ''content''
* Clarify that scrollIntoView() doesn't scroll to children of a ''content-visibility:hidden'' element
* Defined that elements having an ancestor with ''content-visibility: hidden'' don't generate boxes in the top layer
* Defined that being in the top-layer makes an element relevant to the user
* Noted that paint effects with non-local effects can limit certain optimization opportunities.
* Add ContentVisibilityAutoStateChanged event
* Changed how the computed values of the contain property are determined
* Fixed a syntax error in the note about ''contain: content''
* Change terminology: replace "containing box" with "containment box" (in sync with the same improvements made to Level 1)
* Editorial improvements and clarifications to size and paint containment (in sync with the same improvements made to Level 1)
* Be explicit that size containment suppresses natural aspect ratio (in sync with the same improvements made to Level 1)
* Change the animation type of content-visibility from discrete to not animatable
* Add constraint on the timing of the initial determination of visibility for ''content-visibility: auto'' in [[#cv-notes]]