# `react-doctor/forbid-dom-props`

Configure forbidden DOM props via the `forbidDomProps.forbid` setting to keep disallowed attributes off DOM nodes.

- **Status:** Active
- **Category:** Architecture
- **Assessment:** Evidence-required risk
- **Required evidence:** source code, repository context
- **Default configuration:** Enabled
- **Default severity:** warn
- **Scope:** All supported frameworks
- **Active when:** off by default (opt-in)
- **Requirements:** react
- **Priority:** 12 (P3)
- **Source:** oxlint-plugin-react-doctor
- **Rule set:** oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
- **Documentation:** [Official documentation](https://oxc.rs/docs/guide/usage/linter/rules/react/forbid-dom-props)

## Validation prompt

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

Fires only when a prop is configured in the `forbidDomProps.forbid` setting AND that prop name appears as a JSX attribute on a lowercase DOM tag (e.g. <div id> when `id` is forbidden); a per-prop `disallowedFor` list narrows it to specific tags (e.g. `accept` only on <form>). PascalCase components (<Foo>, <this.Foo>), namespaced tags (<fbt:param>), and props delivered only via spread (<div {...props} />) are never flagged.

Suppress when: a forbidden prop that is intentionally required on one element: confirm the team's convention actually forbids it there rather than suppressing blindly, since this rule is purely a project-defined policy with no inherent correctness signal.

## 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, explicit repository policy, relevant exceptions, and required rendered or runtime evidence before deciding the occurrence. This page’s Assessment and Required evidence fields define the review contract.

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

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 or expiry condition. It is not a pass or false positive.

## Fix prompt

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

Remove or rename the forbidden attribute to the project-sanctioned alternative the policy intends: for example swap a banned `className` for the team's preferred prop, or drop `accept` from <form> and place it on the <input> instead (<input type="file" accept="video/*" />). If the prop genuinely belongs there, either narrow the rule's `disallowedFor` list to exclude that tag or add a justified disable comment on that line. See https://oxc.rs/docs/guide/usage/linter/rules/react/forbid-dom-props

## Repository-wide copy prompt

Use this only for a repository-wide pass after validating each occurrence. For one occurrence, use the occurrence-level guidance above.

````text
Fix every confirmed `react-doctor/forbid-dom-props` diagnostic in the current repository.

Required change:
- Remove or rename the forbidden attribute to the project-sanctioned alternative the policy intends: for example swap a banned `className` for the team's preferred prop, or drop `accept` from <form> and place it on the <input> instead (<input type="file" accept="video/*" />). If the prop genuinely belongs there, either narrow the rule's `disallowedFor` list to exclude that tag or add a justified disable comment on that line. See https://oxc.rs/docs/guide/usage/linter/rules/react/forbid-dom-props.

Validation before editing:
Fires only when a prop is configured in the `forbidDomProps.forbid` setting AND that prop name appears as a JSX attribute on a lowercase DOM tag (e.g. <div id> when `id` is forbidden); a per-prop `disallowedFor` list narrows it to specific tags (e.g. `accept` only on <form>). PascalCase components (<Foo>, <this.Foo>), namespaced tags (<fbt:param>), and props delivered only via spread (<div {...props} />) are never flagged.

Suppress when: a forbidden prop that is intentionally required on one element: confirm the team's convention actually forbids it there rather than suppressing blindly, since this rule is purely a project-defined policy with no inherent correctness signal.

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.
- 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: `off by default (opt-in)`.

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.
````