`react-doctor/remotion-no-css-transition`

CSS transition is not frame-driven

Category: Bugs
Severity: error
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: remotion:4
Tags: react-jsx-only
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/remotion-no-css-transition. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

import {
  useCurrentFrame,
  useVideoConfig,
} from "remotion";

const Title = () => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  return (
    <div
      style={{
        opacity: frame < fps ? 0 : 1,
        transition: "opacity 1s",
      }}
    />
  );
};

Corrected pattern

import {
  interpolate,
  useCurrentFrame,
  useVideoConfig,
} from "remotion";

const Title = () => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  const opacity = interpolate(frame, [0, fps], [0, 1], {
    extrapolateRight: "clamp",
  });
  return <div style={{ opacity }} />;
};

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/remotion-no-css-transition diagnostic in the current repository. Required change: - Drive the property from useCurrentFrame() with interpolate() so every rendered frame is deterministic.

Reference transformation:Before:

import {
  useCurrentFrame,
  useVideoConfig,
} from "remotion";

const Title = () => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  return (
    <div
      style={{
        opacity: frame < fps ? 0 : 1,
        transition: "opacity 1s",
      }}
    />
  );
};

After:

import {
  interpolate,
  useCurrentFrame,
  useVideoConfig,
} from "remotion";

const Title = () => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  const opacity = interpolate(frame, [0, fps], [0, 1], {
    extrapolateRight: "clamp",
  });
  return <div style={{ opacity }} />;
};

Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. - Confirm this rule is enabled for the project: remotion:4. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Bugs rules from the rules reference:

react-doctor/remotion-no-css-url-assets: CSS URL asset can flicker in Remotion
react-doctor/remotion-no-module-scope-delay-render: Module-scoped delayRender blocks every composition
react-doctor/remotion-no-native-media-elements: Native media element bypasses Remotion loading
react-doctor/remotion-no-next-image: Next.js Image can flicker in Remotion
react-doctor/remotion-stable-delay-render-handle: delayRender handle is recreated during render

react-doctor/remotion-no-css-transition