This is an umbrella issue for tracking the work on adding TextField to @mui/material-next as part of the Material You effort (#29345)

Material Design 3 TextField specs: https://m3.material.io/components/text-fields/specs

Prerequisites

As TextField is composed from several components, we have issues tracking work for the constituent parts:

• [InputBase][material-next] Add InputBase component #38372
• [FormControl][material-next] Add FormControl component #38411
• [FilledInput][material-next] Add FilledInput component #39052
• [InputLabel][material-next] Add InputLabel component #39512
• [InputAdornment][material-next] Add InputAdornment component #39628 (internally it also depends on Typography)
• [FormHelperText][material-next] Add FormHelperText component #39513
• [OutlinedInput][material-next] Add OutlinedInput component #39695
• [TextField][material-next] Add TextField component #39696

These look related but are not: FormControlLabel, FormGroup

New Features/Breaking Changes

TextField

• Drop the built-in Select #21782
• Drop Standard variant, we were still supporting it even though it was dropped from Material Design 2 (source)
• Rename inputComponent to component [FormControl][material-next] Add FormControl component #39032 (comment)
• Integrate better with <input type="reset"> [TextField] Uncontrolled Input components do not fully reset when inside a <form> with a reset button #39302

FormControl

• Pass disabled attribute if the underlying element is a fieldset [material-ui][Form Control] Native HTML attribute is not supported #38932
• Refactor the context and hook so that it extends Base UI's FormControl to provide Material UI features (discussed in [FormControl][material-next] Add FormControl component #38411)
• Allow rendering a Fragment [FormControl] Cannot render FormControl as React.Fragment #38094

InputAdornment

• [TextField][InputAdornment] InputLabel should not start shrunken if TextField has an InputAdornment #13898