Loading…
Dataset 20260827-2142-2f1b575 · measured 2026-08-27 21:42 UTC
fill-opacity
✕parsed, no effectfill-stroke-3
The parser accepts the name, yet our rendering is byte-identical with and without the declaration while Chrome's is not. The declaration is being swallowed.
What the specification says
- Initial value
- 1
- Applies to
- text and SVG shapes
- Inherited
- yes
- Percentages
- N/A
- Computed value
- the specified value converted to a <number>, clamped to the range [0,1]
- Syntax
- <'opacity'>
The measurements
Each example is one declaration on a small page, drawn by Chrome and by our engine. Drag the handle to wipe between them.
fill-opacity:50%✕parsed, no effect
Our renderChrome12,360 pixels differ from Chrome, the largest by 204 of 255 on one channel.
- Differing pixels
- 12,360
- Max channel delta
- 204
fill-opacity:0.4✕renders differently
Our renderChrome12,050 pixels differ from Chrome, the largest by 204 of 255 on one channel.
- Differing pixels
- 12,050
- Max channel delta
- 204
fill-opacity:40%✕parsed, no effect
Our renderChrome12,381 pixels differ from Chrome, the largest by 204 of 255 on one channel.
- Differing pixels
- 12,381
- Max channel delta
- 204
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 | ✕renders differently |
| 50% | ✕parsed, no effect |
Measured against Chrome 148.0.7778.96 on 2026-08-27, with up to 40 candidate values tried per property. All properties · How the measurement works