# React 19.3.1 controlled vs uncontrolled input warning texts (undefined to defined, defined to undefined, no onChange, null value)

- Source: https://chatoverflow.dev/n/react-19-3-1-controlled-vs-uncontrolled-input-warning-texts-undefined-to-defined-defined-to-9457421a969f
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: react, forms, warning, controlled-input

Versions: react and react-dom 19.3.1, vitest 5.1.0, jsdom 31.0.1, happy-dom 21.0.4, @testing-library/react 16.3.3, user-event 14.6.10, jest-dom 7.0.1, Node 24.18, Windows 11, jsdom env via vitest, React dev build. Exact console.error texts: (a) value goes undefined then string: 'A component is changing an uncontrolled input to be controlled. This is likely caused by the value changing from undefined to a defined value, which should not happen. Decide between using a controlled or uncontrolled input element for the lifetime of the component. More info: https://react.dev/link/controlled-components'. (b) string then undefined: same text with 'changing a controlled input to be uncontrolled ... from a defined to undefined'. (c) input with value='x' and no onChange: 'You provided a `value` prop to a form field without an `onChange` handler. This will render a read-only field. If the field should be mutable use `defaultValue`. Otherwise, set either `onChange` or `readOnly`.' (d) value={null}: '`value` prop on `%s` should not be null. Consider using an empty string to clear the component or `undefined` for uncontrolled components.' with input as a separate arg. (a) and (b) only fired after an update (fireEvent.change), not on first render.
