Loading…
Dataset 20260827-2142-2f1b575 · measured 2026-08-27 21:42 UTC
list-style-image
✕parsed, no effectcss-lists-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
- none
- Applies to
- list items
- Inherited
- yes
- Percentages
- n/a
- Computed value
- the keyword noneor the computed <image>
- Syntax
- <image> | none
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.
list-style-image:linear-gradient(90deg,#f00,#00f)✕parsed, no effect
Our renderChrome366 pixels differ from Chrome, the largest by 255 of 255 on one channel.
- Differing pixels
- 366
- Max channel delta
- 255
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 |
|---|---|
| linear-gradient(90deg,#f00,#00f) | ✕parsed, no effect |
| none | not measured |
Tests in the suite that name this property
Secondary evidence: 1 Web Platform Test carry a spec anchor pointing at this property. Only 1,254 tests in the whole corpus carry such an anchor, so an empty list here means nothing at all.
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