Loading…
Dataset 20261011-0550-f160c57 · measured 2026-10-11 05:50 UTC
stop-opacity
◐matches Chrome on some values1 of 3 examples match Chromesvg
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 3 examples match Chrome. The 2 that do not: stop-opacity:50%, stop-opacity:40% — shown first below, each with its difference map.
The measurements
3 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.
stop-opacity:50%–not implemented
Our renderChrome47,456 pixels differ from Chrome, the largest by 102 of 255 on one channel.
- Differing pixels
- 47,456
- Max channel delta
- 102
stop-opacity:40%–not implemented
Our renderChrome47,474 pixels differ from Chrome, the largest by 123 of 255 on one channel.
- Differing pixels
- 47,474
- Max channel delta
- 123
stop-opacity:0.4≈below the visible threshold
Our renderChrome37,750 pixels differ from Chrome, the largest by 2 of 255 on one channel.
- Differing pixels
- 37,750
- Max channel delta
- 2
Which values were measured
“Supported” on one example means “supported at the value we tried”. The property’s declared grammar has 2 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 |
|---|---|
| 2 | ≈below the visible threshold |
| 50% | –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