New
Introducing React Bench, see how different models perform on React code

react-doctor/no-layout-transition-inline

Review inline transitions of layout properties and preserve the distinction between visual movement and real document reflow

Status
Active
Category
Performance
Assessment
Evidence-required risk
Required evidence
source code, runtime behavior, measurement
Default configuration
Disabled until configured
Default severity
warn
Show technical metadata
Scope
All supported frameworks
Active when
always
Tags
design, test-noise
Priority
44 (P3)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

The detector reports a statically resolved inline style.transition or style.transitionProperty that explicitly names width, height, a min/max size variant, padding, or margin (including side suffixes). It deliberately skips values containing all and cannot inspect stylesheet rules or dynamic strings. Confirm the property is actually interpolated with a positive duration, then inspect the rendered contract: whether siblings must reflow, intrinsic content must reveal, the hit area or clipping changes, and whether a production trace shows material layout cost. A grid-track transition is an intrinsic-size technique that can still perform layout; it is not a compositor fix.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

The design tag controls activation and discovery. It does not determine the rule’s proof class.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Choose the smallest behavior-preserving fix. For a purely visual offset or reveal, establish final geometry and use transform, opacity, or a suitable clip while preserving transform origin, clipping, hit testing, and other transform owners; these properties are broadly compositor-eligible, not guaranteed free. When siblings or intrinsic content must reflow, keep the layout state change and either make it immediate, use a scoped intrinsic-size technique such as a grid-track transition, or use measured layout projection where the installed library supports it. Do not replace width, height, margin, or padding with scale or translate when that changes text geometry, document flow, focus geometry, or interaction. Re-profile when performance is the reason for editing. See https://web.dev/articles/animations-guide

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Fix every confirmed react-doctor/no-layout-transition-inline diagnostic in the current repository.

Required change:

  • Choose the smallest behavior-preserving fix. For a purely visual offset or reveal, establish final geometry and use transform, opacity, or a suitable clip while preserving transform origin, clipping, hit testing, and other transform owners; these properties are broadly compositor-eligible, not guaranteed free. When siblings or intrinsic content must reflow, keep the layout state change and either make it immediate, use a scoped intrinsic-size technique such as a grid-track transition, or use measured layout projection where the installed library supports it. Do not replace width, height, margin, or padding with scale or translate when that changes text geometry, document flow, focus geometry, or interaction. Re-profile when performance is the reason for editing. See https://web.dev/articles/animations-guide.

Validation before editing:

The detector reports a statically resolved inline style.transition or style.transitionProperty that explicitly names width, height, a min/max size variant, padding, or margin (including side suffixes). It deliberately skips values containing all and cannot inspect stylesheet rules or dynamic strings. Confirm the property is actually interpolated with a positive duration, then inspect the rendered contract: whether siblings must reflow, intrinsic content must reveal, the hit area or clipping changes, and whether a production trace shows material layout cost. A grid-track transition is an intrinsic-size technique that can still perform layout; it is not a compositor fix.

Constraints:

  • Make the smallest change that fixes the root cause.
  • Preserve behavior and interfaces unrelated to this diagnostic.
  • Reuse existing project components, utilities, and conventions.
  • Preserve resource ownership and cleanup. Do not move work into a hotter render or frame path.
  • If syntax proves only a candidate cost, require a relevant trace, bundle report, payload measurement, or metric before editing.
  • Without evidence, record Needs evidence. Compare the same scenario before and after; keep the change only when its target metric improves without regression.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not disable the rule or suppress matching code.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.