Loading…
Dataset 20261011-0550-f160c57 · measured 2026-10-11 05:50 UTC
content-visibility
◐matches Chrome on some values1 of 2 examples match Chromecss-contain-2
Some of the examples match Chrome and some do not. The count beside the verdict says how many — 11 of 12 — and the values that differ are listed on the property page. It is neither a pass nor a failure, and filing it under either would be a lie in one direction.
Here: 1 of 2 examples match Chrome. The one that does not: content-visibility:auto — shown first below, each with its difference map.
What the specification says
- Initial value
- visible
- Applies to
- elements for which size containment can apply
- Inherited
- no
- Percentages
- n/a
- Computed value
- as specified
- Syntax
- visible | auto | hidden
The measurements
2 examples, 1 of them matching Chrome, the rest first. Each is one declaration on a small page, drawn by Chrome and by our engine. Drag the handle to wipe between them.
content-visibility:auto–not implemented
Our renderChrome1,402 pixels differ from Chrome, the largest by 45 of 255 on one channel.
- Differing pixels
- 1,402
- Max channel delta
- 45
content-visibility:hidden✓pixel-exact
Our renderChromeIdentical to Chrome: nothing differs, so there is no difference map to show.
- Differing pixels
- 0
- Max channel delta
- 0
Which values were measured
“Supported” on one example means “supported at the value we tried”. The property’s declared grammar has 3 branches; 2 of them carry a measurement. The publishing ceiling is 12 examples per property — a branch past it is left out by our choice, not by accident.
| Value | Measured |
|---|---|
| hidden | ✓pixel-exact |
| visible | not measured |
| auto | –not implemented |
Measured against Chrome 148.0.7778.96 on 2026-10-11, with up to 40 candidate values tried per property. All properties · How the measurement works