animate-elem-34-t

81.3% of the ink matches

fail - measured over 37908 pixels carrying ink in either image.

These results are not meaningful. This check renders a single static frame, and nothing in a test document records which moment in time its reference image was captured at - so a correct SMIL implementation and a broken one are equally likely to mismatch. Animation behaviour is covered by dedicated unit tests instead; see ctgnz/foxglove#208 for a real measurement methodology, still to be worked out.

W3C reference (context only, see #200)

Foxglove

Difference

In the difference panel, red marks pixels that differ beyond tolerance and grey marks matching content. The tinted band, where present, is the <text id="revision"> legend every test carries: it renders in a fallback font this library cannot match, so it is excluded from the comparison entirely rather than failing every test.

What this test checks

The test is passed if all of the following conditions are met: The red path in the shape of the digit "1" morphs continuously over three seconds (from 1s to 4s in document time) to the shape of "2", "3" and then "4". The gray paths show the four shapes and positions that the red path takes as it morphs. Initially, when the document is loaded, of the four paths underneath each of the four digits, the second one is u-shaped, while the other three are square shaped. The first path is red, while the remaining three are gray. From 1s to 2s, the path below the "1" digit is red and square-shaped and the others are gray and u-shaped. From 2s to 3s, the path below the "2" digit is red and square-shaped and the others are gray and u-shaped. From 3s to 4s, the path below the "3" digit is red and square-shaped and the others are gray and u-shaped. From 4s onwards, the path below the "4" digit is red and square-shaped and the others are gray and u-shaped.

View the source document at W3C