why: candidate lacks paint present in reference (0.2%)
Compatibility canary for vertical outside-marker placement. The current fixture gives every item the same directionality as its parent, so it cannot distinguish marker-side:match-parent from match-self; a future semantic fixture must contrast the two directions without treating an exact outside-marker position as normative.
reference dispute: CSS Lists 3 leaves the exact position of outside marker boxes undefined. This fixture does not vary list-item directionality, so match-parent has no observable effect. Chromium 150 reports CSS.supports('marker-side: match-parent') as false and an empty computed value; its PDF is an unsupported-feature compatibility canary, not a normative oracle.
regions (23 total; showing 23 representatives)
Complete component census grouped by dominant raster class; representative details are bounded.
Complete dominant-class aggregates
class
regions
pixels
union bbox (CSS px)
largest px
maximum magnitude
ColorErr
17
829
68,19 → 114,60
275
total 0.4% · largest 0.1%
Missing
3
225
68,46 → 114,60
83
total 0.1% · largest 0.04%
Extra
3
220
69,47 → 115,60
78
total 0.10% · largest 0.04%
Representative region details (worst-first)
class
bbox (CSS px)
area%
magnitude
reason
AntialiasCoverage
68,19 → 83,28
0.1
ΔRGB(-1,-1,-1)
antialiasing coverage residue on a shared outline
AntialiasCoverage
69,59 → 85,60
0.05
ΔRGB(76,76,76)
antialiasing coverage residue on a shared outline
AntialiasCoverage
98,20 → 110,23
0.05
ΔRGB(-40,-42,-44)
antialiasing coverage residue on a shared outline
AntialiasCoverage
70,47 → 84,48
0.04
ΔRGB(89,89,89)
antialiasing coverage residue on a shared outline
Missing
95,52 → 114,53
0.04
candidate lacks paint present in reference (0.04%)
AntialiasCoverage
98,25 → 110,25
0.04
ΔRGB(118,126,131)
antialiasing coverage residue on a shared outline
Extra
97,52 → 115,54
0.04
candidate adds paint absent from reference (0.04%)
Missing
68,58 → 85,60
0.03
candidate lacks paint present in reference (0.03%)
Extra
69,59 → 87,60
0.03
candidate adds paint absent from reference (0.03%)
Extra
70,47 → 85,48
0.03
candidate adds paint absent from reference (0.03%)
Missing
69,46 → 84,48
0.03
candidate lacks paint present in reference (0.03%)
A list styles only ::marker with a 36px font-size while item text remains 20px. Catches: A marker renderer that only recolors markers passes marker color tests but misses marker font metrics.
An ordered list replaces default decimal markers with a generated counter wrapped in square brackets through ::marker content. Catches: A ::marker color-only implementation passes marker styling tests but still emits default 1./2. markers.
The middle li value='7' changes that marker and subsequent items continue from 8. Catches: An ordered-list context that only tracks a running index passes default and start fixtures but ignores per-item value overrides.
A three-item ordered list with the reversed attribute should render 3, 2, 1 markers. Catches: An ol implementation that only handles start passes start fixtures but always counts upward.
A custom @counter-style named checks cycles through two literal symbols for list markers. Catches: Ignoring @counter-style passes built-in marker tests but falls back to disc for author-defined styles.
A custom counter style extends decimal with pad:2 '0', prefix '[' and suffix '] '. Catches: A decimal-only formatter passes decimal-leading-zero and roman fixtures but ignores custom style descriptors.
A generated counter starts at -2 and uses a custom negative descriptor to wrap negative values. Catches: A counter implementation that only formats positive decimal/roman cases passes current fixtures but mishandles negative custom styles.
Each li appends generated text using counter(list-item), matching its ordered-list marker number. Catches: A renderer with an internal list index can paint markers but still resolves counter(list-item) to 0 in content.
An <ol> of ten 40px items spans two pages (CSS Lists 3 §4): counters resolve in document order, not visual layout, so page 2 markers read 6-10 (not a reset to 1). The multi-page harness asserts the page COUNT (2) and diffs both pages; a per-page counter reset would fail.
An ordered list increments list-item by 2 so markers advance 2, 4, 6. Catches: A list renderer with hard-coded +1 indices passes normal lists but ignores author counter-increment on list-item.
A ul sets list-style-type:'-- ' so each marker is a literal two-dash string instead of a disc. Catches: A built-in-only list-style parser falls unknown types back to disc and passes disc/circle/square fixtures.
PASSvisually equivalent · no rejecting defect · thresholded evidence 0.001474% · raw 0.001474% (7 px)lists-counters-list-style-type-cjk-decimal · list-style-type-cjk-decimalPASS via CSS-scale observation: sub-CSS shared-outline coverageMissingmissing 0.002849%ΔE 0.8
Chrome refironpressfull-page >1.0%/channel diff
why: visually accepted coverage phase; raw candidate lacks paint present in reference (0.002849%)
An ordered list uses cjk-decimal markers, which render CJK decimal digits rather than western 1/2/3. Catches: An implementation limited to latin/roman built-ins passes existing list-style-type coverage but falls back to disc or decimal for international styles.
regions (2 total; showing 2 representatives)
Complete component census grouped by dominant raster class; representative details are bounded.
Complete dominant-class aggregates
class
regions
pixels
union bbox (CSS px)
largest px
maximum magnitude
Missing
1
6
20,13 → 20,15
6
total 0.002230% · largest 0.002230%
ColorErr
1
1
20,15 → 20,15
1
total 0.000372% · largest 0.000372%
Representative region details (worst-first)
class
bbox (CSS px)
area%
magnitude
reason
Missing
20,13 → 20,15
0.002230
candidate lacks paint present in reference (0.002230%)
