Loading…
Dataset 20261011-0550-f160c57 · measured 2026-10-11 05:50 UTC
orphans
◐matches Chrome on some values1 of 2 examples match Chromecss-break-4
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: orphans:8 — shown first below, each with its difference map.
What the specification says
- Initial value
- 2
- Applies to
- block containers that establish an inline formatting context
- Inherited
- yes
- Percentages
- n/a
- Computed value
- specified integer
- Syntax
- <integer [1,∞]>
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.
orphans:8✕renders differently
Our renderChrome10,188 pixels differ from Chrome, the largest by 251 of 255 on one channel.
- Differing pixels
- 10,188
- Max channel delta
- 251
orphans:3✓pixel-exact
Our renderChrome4,230 pixels differ from Chrome, the largest by 238 of 255 on one channel.
- Differing pixels
- 4,230
- Max channel delta
- 238
Which values were measured
“Supported” on one example means “supported at the value we tried”. The property’s declared grammar has 1 branch; 1 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 |
|---|---|
| 2 | ✕renders differently |
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