[Bug]: CSS Animation snapshots are leading to false-positives

[enix79]

Describe the bug

We have a spinner component, that is animated via css spin-animation. As far as I can understand (https://www.chromatic.com/docs/animations/) css animations are deactivated on the first frame, just for the reason of not getting false positives. Somehow it is not working on our side and we don't know why.

To Reproduce

• Copy/paste component and story below
• Deploy to Chromatic several times
• Spinner is shown as change, even though the code haven't changed

System

Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.0 - C:\repos\design-system\node_modules\.bin\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (117.0.2045.60)
  npmPackages:
    @storybook/addon-a11y: 7.4.6 => 7.4.6
    @storybook/addon-essentials: 7.4.6 => 7.4.6
    @storybook/addon-interactions: 7.4.6 => 7.4.6
    @storybook/addon-links: 7.4.6 => 7.4.6
    @storybook/addon-styling: 1.3.7 => 1.3.7
    @storybook/blocks: 7.4.6 => 7.4.6
    @storybook/client-api: 7.4.6 => 7.4.6
    @storybook/react: 7.4.6 => 7.4.6
    @storybook/react-vite: 7.4.6 => 7.4.6
    @storybook/testing-library: 0.2.2 => 0.2.2

Additional context

• tailwindcss 3.3.3

Spinner component:

const Spinner: FC = () => {
  return (
    <span role="status">
      <svg
        aria-hidden="true"
        className="w-4 h-4 text-text-on-background-mid animate-spin fill-bg-main"
        viewBox="0 0 100 101"
        fill="none"
        xmlns="http://www.w3.org/2000/svg"
      >
        <path
          d="M100 50.5908C100 78.2051 77.6142 100.591 50 100.591C22.3858 100.591 0 78.2051 0 50.5908C0 22.9766 22.3858 0.59082 50 0.59082C77.6142 0.59082 100 22.9766 100 50.5908ZM9.08144 50.5908C9.08144 73.1895 27.4013 91.5094 50 91.5094C72.5987 91.5094 90.9186 73.1895 90.9186 50.5908C90.9186 27.9921 72.5987 9.67226 50 9.67226C27.4013 9.67226 9.08144 27.9921 9.08144 50.5908Z"
          fill="currentColor"
        />
        <path
          d="M93.9676 39.0409C96.393 38.4038 97.8624 35.9116 97.0079 33.5539C95.2932 28.8227 92.871 24.3692 89.8167 20.348C85.8452 15.1192 80.8826 10.7238 75.2124 7.41289C69.5422 4.10194 63.2754 1.94025 56.7698 1.05124C51.7666 0.367541 46.6976 0.446843 41.7345 1.27873C39.2613 1.69328 37.813 4.19778 38.4501 6.62326C39.0873 9.04874 41.5694 10.4717 44.0505 10.1071C47.8511 9.54855 51.7191 9.52689 55.5402 10.0491C60.8642 10.7766 65.9928 12.5457 70.6331 15.2552C75.2735 17.9648 79.3347 21.5619 82.5849 25.841C84.9175 28.9121 86.7997 32.2913 88.1811 35.8758C89.083 38.2158 91.5421 39.6781 93.9676 39.0409Z"
          fill="currentFill"
        />
      </svg>
      <span className="sr-only">Lade...</span>
    </span>
  );
};

Story:

import { Meta, StoryObj } from "@storybook/react";
import SpinnerComponent from "./Spinner";

export default {
  component: SpinnerComponent,
} as Meta;

export const Spinner: StoryObj = {};

[shilman]

Closing as this seems like more of a Chromatic issue than a Storybook one.

The Chromatic team would be happy to help you on the chromatic.com Intercom chat.