Bug: Uncontrolled `<input />` element has value attribute removed

[imjordanxd]

React version: React 19

Steps To Reproduce

1. Pass an value={undefined} as a prop to an <input /> element
2. Observe the DOM and see the value attribute is absent

Link to code example:

React 18

React 19

The current behavior

React 18 passed a booleanish attribute i.e. <input value />. React 19 omitted the attribute altogether i.e. <input />. This is causing a lot of failures in our snapshot tests. I'm not sure if this behaviour is expected in React 19 and I can't find anything in the release notes apart from this loosely related PR. If this behaviour is expected in 19, it would be great to mention that somewhere!

[narekmalk]

Can I take this issue?

[ronak-create]

Use defaultValue Instead of value

If you're dealing with uncontrolled inputs:

<input defaultValue={someValue} />

• defaultValue does suffer from the undefined issue in React 19.
• Useful for forms where React doesn't need to control the value.

[codeAdityagithub]

It is expected behaviour, as falsy values for attributes won't parse those values and thus not appear on the dom.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[imjordanxd]

Any documentation or acknowledgement of this behaviour would be appreciated

[Shonferns004]

Hello! 👋 I came across issue and would love to work on this. I’ve set up the repo locally and started digging into it.

Just wanted to check in before starting — is anyone already working on this? If not, I’d love to take it up.

Thanks!

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!