Dataset 20261001-0535-e08c90a · measured 2026-10-01 05:35 UTC

Paint api

0 tests judged in this suite · 116 not judged.

0.0%0 of 8 subtests

Coverage — 5.6%: of the 144 subtests wpt.fyi runs in this directory we judge 8. The rest we do not run at all, so no figure above speaks for them.

0Passingrendered pixel-identical to the reference, within the test's own fuzz allowance

0Failingevery one of them listed below, with the evidence

116Not judgedneeds JavaScript, interaction or a draft feature — a PDF engine has none

Every test in this suite

All 116 of them, grouped by the directory the corpus keeps them in — passes included. Open a directory to see what each test checks; open a test to see our render, the reference, the pixels that differ, and the source of both files.

116 tests in 2 directories

These are web-platform-tests files, unchanged. How the browsers score on the same suite · the suite upstream

Judged by assertions

1 files in this suite state what they expect in the markup or as a parser assertion rather than as a second rendering. Each one counts as its subtests in the figures above.

File	Subtests	Verdict
parsing/paint-function-valid.https.html	0/8	8 fail

Dataset 20261001-0535-e08c90a · measured 2026-10-01 05:35 UTC

Loading…