Loading…
Loading…
Dataset 20261011-0550-f160c57 · measured 2026-10-11 05:50 UTC
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: 2 of 3 examples match Chrome. The one that does not: -webkit-box-shadow:10px 10px 12px #e07a1f — shown first below, each with its difference map.
3 examples, 2 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.
-webkit-box-shadow:10px 10px 12px #e07a1f✕renders differently
Our renderChrome17,191 pixels differ from Chrome, the largest by 25 of 255 on one channel.
-webkit-box-shadow:14px 14px 0 8px #e07a1f✓pixel-exact
Our renderChromeIdentical to Chrome: nothing differs, so there is no difference map to show.
-webkit-box-shadow:14px 14px 0 #e07a1f✓pixel-exact
Our renderChromeIdentical to Chrome: nothing differs, so there is no difference map to show.
“Supported” on one example means “supported at the value we tried”. The property’s declared grammar has 3 branches; 3 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 |
|---|---|
| 14px 14px 0 #e07a1f | ✓pixel-exact |
| 10px 10px 12px #e07a1f | ✕renders differently |
| 14px 14px 0 8px #e07a1f | ✓pixel-exact |
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