[interacsean]

Decision record and prototype for making Input Field-aware (option A). Follows #629.

Decision record

decisions/input-field.md records why option A (rewire Input in place, next minor, released as a fix) was chosen over adding a separate InputField, or changing only the docs and warnings.

Prototype (not ready to merge as-is)

• Input renders Base UI's Field.Control. Inside a Field.Root it links the label, description and error, takes the field's name and disabled, and submits through Form.
• When Field.Control renders it (render={<Input />}), Input keeps the old native element. The field still has one control, and a deprecation warning logs once per page.
• input-field.test.tsx covers the common ways Input is composed with Field.
• /showcase/input-field in the vite example shows the before and after side by side for 11 cases.

Notable result: noValidate does not stop Field validation, so a newly wired Input with type="email", min/max or required can now block onFormSubmit.

🤖 Generated with Claude Code

[github-actions]

Code Metrics Report

	main (cc749d5)	#630 (d15c6d5)	+/-
Coverage	89.3%	89.3%	+0.0%
Test Execution Time	2m54s	2m43s	-11s

Details

  |                     | main (cc749d5) | #630 (d15c6d5) |  +/-  |
  |---------------------|----------------|----------------|-------|
+ | Coverage            |          89.3% |          89.3% | +0.0% |
  |   Files             |            228 |            229 |    +1 |
  |   Lines             |           7241 |           7252 |   +11 |
+ |   Covered           |           6471 |           6482 |   +11 |
+ | Test Execution Time |          2m54s |          2m43s |  -11s |

Code coverage of files in pull request scope (100.0% → 100.0%, patch 100.0%)

Files	Coverage	+/-	Patch Coverage	Status
packages/core/src/components/field/field.tsx	100.0%	0.0%	-	modified
packages/core/src/components/field/inside-field-control.ts	100.0%	+100.0%	100.0%	added
packages/core/src/components/input/input.tsx	100.0%	0.0%	100.0%	modified

---

Reported by octocov

[interacsean]

This is an impact assessment of fixing the odd-one-out unconnected nature of Input component, so that it is aware of Field, and its intended usage aligns with all other form input components we provide.

The prototype included in this PR (now) handles the situation where Input is provided as the render prop of Field.Control. Field.Control looks for this anti-pattern, sorts it out internally and emits a deprecation warning. This is largely to reduce the impact on the large number of consumers who already use the pattern we are moving away from

There are a number of implementations that will require a little more hand-holding, but it is manageable

(My guided) claude findings follow: