react-doctor/no-focus-in-animation-completion-handler
Focus waits for animation completion
- Category: Accessibility
- Severity: warn
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: always
- Tags: design, react-jsx-only
- Default: Disabled until configured
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/no-focus-in-animation-completion-handler. 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 { useRef } from "react";
const Dialog = () => {
const inputRef = useRef(null);
return <>
<input ref={inputRef} />
<div onAnimationEnd={() => inputRef.current.focus()} />
</>;
};Corrected pattern
const Dialog = ({ isOpen }) => {
const inputRef = useRef(null);
useEffect(() => {
if (isOpen) inputRef.current?.focus();
}, [isOpen]);
return <input ref={inputRef} />;
};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
Reference transformation:Before:react-doctor/no-focus-in-animation-completion-handler diagnostic in the current repository.
Required change:
- Move focus when interaction state changes, not when animation completes. Reduced or canceled motion must not block focus.import { useRef } from "react";
const Dialog = () => {
const inputRef = useRef(null);
return <>
<input ref={inputRef} />
<div onAnimationEnd={() => inputRef.current.focus()} />
</>;
};const Dialog = ({ isOpen }) => {
const inputRef = useRef(null);
useEffect(() => {
if (isOpen) inputRef.current?.focus();
}, [isOpen]);
return <input ref={inputRef} />;
};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.
- Use existing brand assets, product facts, content, and design tokens.
- Do not invent claims, customer data, typefaces, or artwork.
- Preserve accessible names, focus order, keyboard behavior, and touch access not targeted by this rule.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.
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.
Related rules
More Accessibility rules from the rules reference:
react-doctor/no-focusable-content-in-aria-hidden: aria-hidden subtree contains focusable contentreact-doctor/no-focusable-content-in-role-text: Focusable control inside role=textreact-doctor/no-gray-on-colored-background: Use a darker shade of the background color for text, or white/near-white for contrast. Gray text on colored backgrounds looks washed outreact-doctor/no-hover-only-reveal: Content is revealed only on hoverreact-doctor/no-inert-pointer-affordance: Pointer cursor has no interaction