[core] Decide if a value belongs in props or context

[mbrookes]

I think the actual code smell is computing some variable from context and props. Just like a component instance should either read from state or props (but not switch between) we shouldn't listen to context and props. It's a general issue with our form components where <FormControl disabled><Input disabled={false} /></FormControl> is allowed for some reason. The disabled state should live at a single point.

In v5 we should revisit this and decide if something lives in props or context.

Originally posted by @eps1lon in #19319 (comment)

Related:

• TextField with focused and disabled causes an infinite render

[michaldudak]

In MUI Base, if an input is inside a FormControlUnstyled, it cannot have its own props (it applies to the props that can be set on a form control). Having props in such case will trigger a warning.