Bug: defaultValue property missing on select element ref

React version: 18.2.0

Steps To Reproduce

1. Set a defaultValue on a <select /> element.
2. After the element mounts, try to access that defaultValue through a ref of the element.

TypeScript is also missing the definition for defaultValue on HTMLSelectElement type

Link to code example: https://codesandbox.io/s/elated-orla-0p3dw7?file=/src/App.js

The current behavior

defaultValue always returns undefined

The expected behavior

defaultValueshould return the defined value

[vkurchatkin]

I know I can read selected property, but React strongly advises against using it in the first place.

React advises you agains using selected as React prop, nothing more. It is unreasonable to expect it to actually add a nonexistent property to a DOM node. If you want to work with DOM directly it is up to you to handle differences like this

[antonio-costa]

I know I can read selected property, but React strongly advises against using it in the first place.

I’m trying to create a reusable hook for uncontrolled forms (similar to React Hook Form) and I’m comparing the current value with the default value in order to check whether an input has been changed. This comparison can be done anywhere inside the form context, which may have several components nested and diverging trees.

My solution is to simply keep a reference to the fields registered in the form and access the DOM when I need information. That way I can freely change inputs without any unnecessary re-renders.

I can try to find a way around this, sure, but it just seems inconsistent that I’m advised against the selected property in favor of defaultValue property, but that one is not provided anywhere in the DOM just as selected property is.