react-doctor/no-invalid-progress-range
Progress value falls outside its range
- Category: Accessibility
- Severity: error
- Source:
oxlint-plugin-react-doctor - Framework: global
- Enabled when: react
- Default: Enabled
Validate the diagnostic
Confirm the reported code matches this rule before you edit it.
Confirm the reported code matches react-doctor/no-invalid-progress-range. 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
<progress min={0} max={100} value={120} />Corrected pattern
<progress min={0} max={100} value={100} />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-invalid-progress-range diagnostic in the current repository.
Required change:
- Keep determinate progress values within a valid positive range so visual and assistive feedback report the same advancement.<progress min={0} max={100} value={120} /><progress min={0} max={100} value={100} />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.
- 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.
- Confirm this rule is enabled for the project:
react.
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-invisible-focus-control: Invisible native control lacks keyboard focus treatmentreact-doctor/no-justified-text: Use `text-align: left` for body text, or add `hyphens: auto` and `overflow-wrap: break-word` if you must justifyreact-doctor/no-low-contrast-inline-style: Low-contrast text in inline stylereact-doctor/no-multiple-main-landmarks: View contains multiple main landmarksreact-doctor/no-multiple-unlabeled-navigation-landmarks: Repeated navigation landmarks need unique names