Loading…
Dataset 20261011-0550-f160c57 · measured 2026-10-11 05:50 UTC
border-block-color
◐matches Chrome on some values1 of 2 examples match Chromecss-borders-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: border-block-color:#e07a1f — shown first below, each with its difference map.
What the specification says
- Initial value
- see individual properties
- Applies to
- see individual properties
- Inherited
- see individual properties
- Percentages
- see individual properties
- Computed value
- see individual properties
- Syntax
- <'border-top-color'>{1,2}
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.
border-block-color:#e07a1f✕renders differently
Our renderChrome84 pixels differ from Chrome, the largest by 64 of 255 on one channel.
- Differing pixels
- 84
- Max channel delta
- 64
border-block-color:rgba(224,122,31,0.45)≈below the visible threshold
Our renderChrome8,414 pixels differ from Chrome, the largest by 3 of 255 on one channel.
- Differing pixels
- 8,414
- Max channel delta
- 3
Which values were measured
“Supported” on one example means “supported at the value we tried”. The property’s declared grammar has 2 branches; 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 |
|---|---|
| #e07a1f | ✕renders differently |
| linear-gradient(90deg,#f00,#00f) | not measured |
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